Quantcast

New build system - questions, missing bits

classic Classic list List threaded Threaded
2 messages Options
scdr scdr
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

New build system - questions, missing bits


Some questions about few things that seem to be missing or work differently with the new build system.

All of the testing for this is on the LM3S platform (e.g. EK-LM3S8962).

1) How do I include the bitarray module in a build?
Under scons the bitarray module was included automatically.
Under the lua build system it is not included, and I have not figured out any way to get it included,
short of editing the build system files.
e.g. edit config/modules.lua
add
  bitarray = {},
under
 local elua_generic_modules = {

2) Interrupt constants seem to be missing from cpu module.
If I build it with elua interrupts on, using scons the cpu module would have constants like cpu.INT_TMR_MATCH,
with the lua build system these constants are not generated.

3) Why was linenoise turned off by default for the lm3s processors?
Not a big deal, since as long as one knows that it exists, one can turn it back on.  
But I was curious if there was a particular reason to not use linenoise on the lm3s platform.  

4) How do you make the new build system only compile the files you are actually using?
Even if you tell it to not use a particular module (e.g. i2c, or, as noted above bitarray, which is not used at all)
the lua build scripts still compile the .c file.  Seems like a waste of time to keep recompiling things that are not
being used.  I did not check to see if scons did this also, just used to build systems knowing enough to only
compile the files that are actually used by a particular target.

  Thanks
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
BogdanM BogdanM
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: New build system - questions, missing bits

Hi,


On Mon, Aug 19, 2013 at 4:29 AM, <[hidden email]> wrote:

Some questions about few things that seem to be missing or work differently with the new build system.

All of the testing for this is on the LM3S platform (e.g. EK-LM3S8962).

1) How do I include the bitarray module in a build?
Under scons the bitarray module was included automatically.
Under the lua build system it is not included, and I have not figured out any way to get it included,
short of editing the build system files.
e.g. edit config/modules.lua
add
  bitarray = {},
under
 local elua_generic_modules = {

bitarray is not an "official" module (because it doesn't have any associated documentation), so it was not included in the configurator. I need to fix this (both the documentation and the configurator side).

2) Interrupt constants seem to be missing from cpu module.
If I build it with elua interrupts on, using scons the cpu module would have constants like cpu.INT_TMR_MATCH,
with the lua build system these constants are not generated.

That was an error in the LM3S8962 CPU header file, fixed on master now,
 

3) Why was linenoise turned off by default for the lm3s processors?
Not a big deal, since as long as one knows that it exists, one can turn it back on.  
But I was curious if there was a particular reason to not use linenoise on the lm3s platform.  

Nope, no particular reason, except for saving some flash / RAM.


4) How do you make the new build system only compile the files you are actually using?
Even if you tell it to not use a particular module (e.g. i2c, or, as noted above bitarray, which is not used at all)
the lua build scripts still compile the .c file.  Seems like a waste of time to keep recompiling things that are not
being used.  I did not check to see if scons did this also, just used to build systems knowing enough to only
compile the files that are actually used by a particular target.

There is no way to do this right now, the build system doesn't try to do any optimizations on the compilation time. It simply scans the sources and compiles all of them. Something that will be addressed in the future (but with low priority).

Best,
Bogdan
 

  Thanks
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev


_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
Loading...