[Distutils] handling complex link/library specifications

[andrew.macintyre@aba.gov.au]

[repost as my original was misdirected - apologies to -admin. am]

Thanks for your response.

the -R option can certainly be handled that way, but the toggling of the
static/dynamic library loading I don't think can be.  Mind you, I'm no guru on
the subject.

-------------------------------------------------------------
Andrew MacIntyre                \ andrew.macintyre@aba.gov.au
Planning & Licensing Branch      \ Tel: +61 2 6256 2812
Australian Broadcasting Authority \ Fax: +61 2 6253 3277
---------- Original Text ----------

From: Harry Henry Gebel <hgebel@inet.net>, on 24/05/00 16:35:

On Wed, May 24, 2000 at 02:28:36PM +0000, Andrew MacIntyre wrote:
> Unfortunately, the commercial package I'm dealing with has a long list of
> libraries required to be linked, with several specified static and the rest
> dynamic.
> 
> The recommended library spec (for Solaris, which is what I'm working with at
> the moment) looks something like this:
> 
> -l<lib> ... -l<lib> -Bstatic -l<lib>... -l<lib> -Bdynamic -l<lib>...-l<lib>
> -R<path>
>
> What would be the recommended way to deal with this, if Distutils in its
> current form can handle this situation?

The CVS version (I think you have to get it from SourceForge) should except
the CFLAGS environment variable, I don't know if this will help you or not.

-- 
Harry Henry Gebel, Senior Developer, Landon House SBS
West Dover Hundred, Delaware

_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@python.org
http://www.python.org/mailman/listinfo/distutils-sig