On Sun, Feb 9, 2020 at 11:47 AM Peter Kovacs <pe...@apache.org> 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 dependencies with "scons -u --tree=all" run in a
module:
+-fileaccess
+-fileaccess/SConscript
+-fileaccess/inc
| +-fileaccess/inc/fileaccess
| +-fileaccess/inc/fileaccess/dllapi.h
+-fileaccess/source
| +-fileaccess/source/FileAccess.cxx
| +-fileaccess/source/fileacc.xml
+-fileaccess/util
+-fileaccess/util/fileacc.component
Dependencies between modules can be seen in main/ with "scons
--tree=prune", which autodetects tons of headers, libraries, xml, etc. in
solver/, with transitive dependencies.
There are others, see
https://scons.org/doc/production/HTML/scons-user.html#chap-troubleshooting
>
> Also do you have an idea how to handle IDLs with scon? That would be
> awesome.
>
>
You mean the idlc + regmerge + cppmaker/javamaker toolchain? It should be
fairly easy, given I already ported part of it to Ant before
(main/solenv/ant/idl.xml), although that didn't do header dependencies in
.idl files.
> All the best
> Peter
>
>
Damjan
