build system q's
Locked
|
Hi there - I've just been poking around the eLua docs to get started (most everything looks great!) and had a question about the build system.
It appears that in order to configure a build for a particular platform, the recommended practice is to modify config files within the SVN tree. Is this correct? If so, it seems a little less than ideal in a couple cases: * I have more than one configuration for a platform that I'd like to maintain * I would like to maintain my platform configurations in my own source control system, without putting all of eLua in there as well * I would like to avoid conflicts when updating eLua SVN when my local configuration edits are in place For exploratory purposes, it's of course fine to start hacking around in a downloaded bundle of the eLua src tree, but if I were to try to maintain a project building against it, I'd hope to find some better solutions to these issues. Thanks for any tips! Liam _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
Hi,
On Mon, Oct 4, 2010 at 7:08 PM, Liam Staskawicz <[hidden email]> wrote:
Hi there - I've just been poking around the eLua docs to get started (most everything looks great!) and had a question about the build system. Thank you very much for your feedback. You are perfectly right, and we are aware of this. Changing this is something we're working on right now; most likely we'll keep the static configuration data (things like number of UARTs/PIOs and so on) in platform_conf.h, and move the board-specific configuration somewhere else. Until then, you could either keep on hacking the platform configuration files (sorry about that), or try our Web builder: http://builder.eluaproject.net/web/start.lua?control=user&act=index It doesn't have the same granularity as editing the configuration files by hand, but it might be good enough for you. Best, Bogdan _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
In reply to this post by Liam Staskawicz
> Date: Mon, 4 Oct 2010 19:16:05 +0300 > From: Bogdan Marinescu <[hidden email]> > To: "eLua Users and Development List (www.eluaproject.net)" > <[hidden email]> > Subject: Re: [eLua-dev] build system q's > Message-ID: > <[hidden email]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > On Mon, Oct 4, 2010 at 7:08 PM, Liam Staskawicz <[hidden email]> wrote: > >> Hi there - I've just been poking around the eLua docs to get started (most >> everything looks great!) and had a question about the build system. >> >> It appears that in order to configure a build for a particular platform, >> the recommended practice is to modify config files within the SVN tree. Is >> this correct? If so, it seems a little less than ideal in a couple cases: >> * I have more than one configuration for a platform that I'd like to >> maintain >> * I would like to maintain my platform configurations in my own source >> control system, without putting all of eLua in there as well >> * I would like to avoid conflicts when updating eLua SVN when my local >> configuration edits are in place >> >> For exploratory purposes, it's of course fine to start hacking around in a >> downloaded bundle of the eLua src tree, but if I were to try to maintain a >> project building against it, I'd hope to find some better solutions to these >> issues. Thanks for any tips! >> > > Thank you very much for your feedback. You are perfectly right, and we are > aware of this. Changing this is something we're working on right now; most > likely we'll keep the static configuration data (things like number of > UARTs/PIOs and so on) in platform_conf.h, and move the board-specific > configuration somewhere else. Until then, you could either keep on hacking > the platform configuration files (sorry about that), or try our Web builder: > > http://builder.eluaproject.net/web/start.lua?control=user&act=index > > It doesn't have the same granularity as editing the configuration files by > hand, but it might be good enough for you. > > Best, > Bogdan > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <https://lists.berlios.de/pipermail/elua-dev/attachments/20101004/86e127b4/attachment-0001.html> > > ------------------------------ > > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev Great - thanks for the quick response. Glad to know this is in the works, and happy to continue hacking for now :) By the way, is there an issue tracker to follow the progress of things like this? Liam _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
http://tracker.eluaproject.net/ Just not exactly very active (or 100% functional) right now :) We still have to make it official. Best, Bogdan _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
«
Return to eLua Development
|
1 view|%1 views
| Free forum by Nabble | Edit this page |