[Scons-users] Dealing with headers appearing from Command builders

[mg at ncp-e.com]

Hi Dirk,

thank you for your input.

> Ditching the Command approach, and implementing customized Emitters
> for your package Builder(s) is probably the way to go.

Okay if I understand you right you suggest writing a fully fledged
Builder and Emitter that gives SCons all the information to correctly
understand what happens. I've done this already for other, simpler
cases.

But as I see it my problem is - even if using an Emitter - that I need
to know in advance what headers at what locations will result from
third-party package builds.

For example, many third party packages use autotools as a build system.
So my current Command builder fetches some version of the package
archive, extracts it, calls configure, make and make install and only
then I really know what the resulting output is.

The input file, like some "package.tar.gz" results in a directory
containing a bunch of headers and libraries etc. The process
from input to output is pretty much opaque to me until the whole thing
is finished.

Knowing this only after the target is built doesn't really help me in
the context of an Emitter or am I missing something?

Thanks and regards,

Matthias

-- 
Matthias Gerstner, Dipl.-Wirtsch.-Inf. (FH)
Entwicklung
 
NCP engineering GmbH
Dombühler Straße 2, D-90449, Nürnberg
Geschäftsführer Peter Söll, HRB-Nr: 77 86 Nürnberg
 
Telefon: +49 911 9968-153, Fax: +49 911 9968-229
E-Mail: Matthias.Gerstner at ncp-e.com
Internet: http://www.ncp-e.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20150408/ada3d6b7/attachment.pgp>