|
undefined parse transform 'tools'
|
|
01-05-2017, 07:08 PM
Post: #4
|
|||
|
|||
|
RE: undefined parse transform 'tools'
Why would I want to use 'make' to compile a single file to move into the Wings plugin directory? Have plugins become so intertwined with the application code that they can't be independently compiled?
I also have to admit that I haven't used 'make' for many years. As a newcomer to Erlang I'd rather focus on learning Erlang and the Wings code base rather than the complexities of the development environment. My modus operandus is always KISS. There is a parse_transform function in /intl_tools/tools.erl. I can locally compile that without error. I wonder if the error is in reference to this parse_transform rather than the compile function I noted in OP. I suspect the real issue is that erlc just isn't finding the correct included files. So a env path issue? Does erlc accept some type of path parameter? --jeff |
|||
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
undefined parse transform 'tools' - kugelfang - 01-05-2017, 12:55 PM
RE: undefined parse transform 'tools' - ggaliens - 01-05-2017, 02:47 PM
RE: undefined parse transform 'tools' - dgud - 01-05-2017, 05:44 PM
RE: undefined parse transform 'tools' - kugelfang - 01-05-2017 07:08 PM
RE: undefined parse transform 'tools' - dgud - 01-05-2017, 09:07 PM
|
User(s) browsing this thread: 1 Guest(s)



