It may be that it's time to consider an interpose library or truss and monitor 
the open/create/delete/rename operations undertaken by the build command, and 
log those. This would also work nicely for java and such things as unit tests 
and scripts which can be tricky to get correct dependencies for in an automated 
way.

That's the way some other make tools work and claim (fairly) that they get 100% 
accurate dependencies. I still like the scanning idea of scons, but that's 
mainly because you can deduce which headers you actually need to build during 
the build process.
----- Original Message -----
From: scons-dev@scons.org
To: scons-dev@scons.org
At: Nov 16 2012 14:18:23

On Wed, 2012-11-14 at 18:10 +0100, Dirk Bächle wrote:
> Hi Russel,
> 
> and what exactly would be a problem for SCons when trying to build 
> Ceylon projects? Can we extract requirements for SCons from it?

Ceylon take various source files in and generates a tree of files where
the names of the resultant files bear no obvious relationship to the
source. Moreover this is a many-to-many mapping. Effectively the
compiler creates an internal indexed database rather than per file/class
compilation products.

On the one hand this is so far from the C/C++/Fortran/D model that there
is no hope of compromise. On the other hand it maybe that the Ceylon
compilation database structure is actually very simple and can be dealt
with by having quasi-hardwired dependencies.

Database file names are module structured so it may be that the database
structure is deducible using a SCons scanner over the incoming source.

I would be more motivated to do something about this if there were an
Emacs mode for Ceylon. Currently they are only interested in using
Eclipse.

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Attachment: signature.asc
Description: Binary data

Attachment: 2745336642428001.txt
Description: Binary data

_______________________________________________
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Reply via email to