On 09.04.2013 14:18, Tobias Hansen wrote:
> On 04/09/2013 10:26 AM, Tobias Hansen wrote:
>>>
>>> a build system for sage ("the library") could be used to switch between
>>> system headers/libraries and stuff installed to /some/sage/prefix.
>>> in order to make use of these switches from sage ("the operating
>>> system"), the toplevel install script must be able process switches like
>>> --with-ntl=/usr/include to pass to the spkg compilation, which in turn
>>> means *all* spkgs must understand such flags (doesn't it?).
>>
>> No, the toplevel install script must just be able to skip the
>> compilation of these spkg's. And tell the Sage library to use the
>> libraries that are available and were compiled independently.
>>
>
> I get it, you are talking about dependencies between spkg's. Yes that
> would require a central mechanism in Sage that provides all spkgs with
> the information where the other stuff is, if we really want the
> possibility to mix spkgs and system libraries.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
