On Sun, Feb 9, 2020 at 11:47 AM Peter Kovacs wrote:
> Sounds nice.
>
> Thank you.
It would be great to have a debug output that can be checked to check which
> dependencies have been pulled. For me a declarative output would be cool to
> understand some code.
>
>
You can see within-module
Sounds nice.
It would be great to have a debug output that can be checked to check which
dependencies have been pulled. For me a declarative output would be cool to
understand some code.
Also do you have an idea how to handle IDLs with scon? That would be awesome.
All the best
Peter
Am 9.
I've implemented static libraries, added linker version scripts, and made
some cleanups, and 22 modules can now be converted to SCons (up from 19 a
week ago).
AllLangResTarget is the next big target, and it seems exceptionally
complicated, with 3 layers of intermediate targets: .src
Hi
I've just pushed a "scons-build" branch.
The build infrastructure is in main/scons. Python and SCons have to be
installed system-wide and available in $PATH. Currently we require Python
3, but that's easy to change.
So far main/fileaccess has been converted to SCons as a test. Its gbuild
Hi Damjan,
Let's try it. But I suggest to push to an own branch. There is no worth in
trying and getting stuck in the same spot.
Merge is done quickly. And it is great if others can have a look, too.
All the best
Peter
Am 1. Februar 2020 13:36:42 MEZ schrieb Damjan Jovanovic :
>Hi
>
My opinion, which might be not worth much, being the opinion of an occasional
dabbler, is the current build system looks unworkable, and that you
shouldn't wait for some communal sanction (which might never come), but just
go ahead and convert to some workable state whatever is there to convert.
Hi
gbuild has become an unmaintainable nightmare. While there are only 37
internal dmake modules left (+ another 37 external modules), I cannot
motivate myself to convert even 1 more. At my development speed of about 2
lines of code every 8 hours, gbuild is a disaster that wastes unbelievable
