build_idl.sh portability

Andrew Bartlett abartlet at samba.org
Sat Jun 2 00:59:51 MDT 2012


David,

I wonder if we could revert the changes you made for bug
https://bugzilla.samba.org/show_bug.cgi?id=8865

It uses some complex shell scripting, and causes issues on Tru64, which
in turn makes it harder to compare the true portability or otherwise of
the waf and autoconf builds. 

https://build.samba.org/build.cgi/build/a029088ee29607e8afe0b15154cfc80be698c21a

Perhaps we could replace it with having ./autogen.sh simply
unconditionally rebuilding the IDL?

Then, given that pidl (and even IDL) changes are rare, it seems
reasonable to me that developers should just run ./autogen.sh if it
changes.  

If we want file-time based dependencies, then we should use make (that
is what is is for, isn't it?), rather than having a mini-build system in
a shell script.  Conceptually I would prefer that we did our perl-based
building in either Makefile.in or autogen.sh, but not both. 

Volker,

I've CC'ed you as this is essentially an autoconf internal build issue.
I just came across it while trying to compare the outputs.  

What do you both think?

Thanks,

Andrew Bartlett
-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org



More information about the samba-technical mailing list