svn commit: samba r4982 - in branches/SAMBA_4_0/source: build/smb_build scripting/swig

[Stefan (metze) Metzmacher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tpot at samba.org schrieb:
| Author: tpot
| Date: 2005-01-25 11:21:25 +0000 (Tue, 25 Jan 2005)
| New Revision: 4982
|
| WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba&rev=4982
|
| Log:
| Start to move swig dependencies into new build system.  Unfortunately
| I can only get something useful happening by using the BINARY keyword
| as nothing else seems to generate dependency lists that can be used
| when linking the swig shared libraries.  Anyway this is a lot nicer
| than having lots of junk in makefile.pm.

You should try to use the LIBRARY keyword.

what are the generated output files? which will be installed by make install

are this the .so files or .i or .py or .pyc files

and what is the way to get this files( what are the logical steps to get them?)

do we just need '/usr/bin/swig' for all this?

I want to try to understand that stuff and then we could find a way to integrate this properly into
the build system

- --
metze

Stefan Metzmacher <metze at samba.org> www.samba.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows XP)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB9mN9m70gjA5TCD8RAoZoAJ912a1owSP5MjfimS17vulHP+CAgACgjSD4
0p9T/pO0thiu4ae35xmbo+c=
=mWg8
-----END PGP SIGNATURE-----