Re: [Alephmodular-devel] Preferences Update - library choice: expat

[Aaron D. <ag...@co...>]

Well, you already know my thoughts on the subject, so I won't bother 
repeating them.

On Wednesday, December 17, 2003, at 01:09 PM, Br'fin wrote:

> I await other people's thoughts and comments on where the recommended 
> place to setup libraries for usage should be. In the meantime, I will 
> probably begin work on CPreferencesWriter_Plist which wouldn't need 
> the library.
>
> -Jeremy Parsons
>
> On Dec 16, 2003, at 1:16 PM, Br'fin wrote:
>
>>
>> On Dec 16, 2003, at 9:33 AM, Timothy Collett wrote:
>>
>>> On Dec 16, 2003, at 7:15 AM, Br'fin wrote:
>>>
>>>> *mutter mutter grumble*
>>>>
>>>> It would figure that autoconf's tools don't like Application 
>>>> Support. Even when you do something like:
>>>> ./configure --prefix='"/Library/Application 
>>>> Support/Expat/expat-1.95.7/"'
>>>>
>>>> On the other hand, I do agree that Application Support itself was 
>>>> never quite right. /Library/Libraries seems a little redundant. So 
>>>> how about /Library/Development?
>>>>
>>>
>>> #1: did you try ./configure --prefix=/Library/Application\ 
>>> Support/Expat/expat-1.95.7/ ?
>>
>> That only gets the prefix past the initial command line. It then gets 
>> dropped into scripts relatively unescaped and certainly unquoted. So 
>> you get past the initial step to have the setup still falter and 
>> miswork.
>>
>>> #2: Since expat's so small, why not just make it part of AM?  That 
>>> means 1 less thing that people have to have installed to run it, 
>>> which makes people more likely to want to install it--less hassle 
>>> for those who don't understand libraries and Unixland and such.
>>
>> My plan with expat is to link it in statically. Thus there's nothing 
>> for the end-user to install. I whole heartedly agree that the user 
>> shouldn't have to look for other libraris to install first before 
>> they run the application
>>
>> All this business with /Library/Development or /Library/Application 
>> Support is specifically for the AM developers. Specifically, I'm 
>> applying what I did to standardize the location of Lua and Speex 
>> libraries under OSX for AlephOne to what I'm doing here for 
>> AlephModular. I'm also trying to get consensus, and smooth out 
>> wrinkles.
>>
>> -Jeremy Parsons
>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: IBM Linux Tutorials.
>> Become an expert in LINUX or just sharpen your skills.  Sign up for 
>> IBM's
>> Free Linux Tutorials.  Learn everything from the bash shell to sys 
>> admin.
>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
>> _______________________________________________
>> Alephmodular-devel mailing list
>> Ale...@li...
>> https://lists.sourceforge.net/lists/listinfo/alephmodular-devel
>>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for 
> IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys 
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Alephmodular-devel mailing list
> Ale...@li...
> https://lists.sourceforge.net/lists/listinfo/alephmodular-devel
>
>
-- 
     __                        __
    /  )                      /  )
   /--/ __.  __  ________    /  / __. , __o  _  _
  /  (_(_/|_/ (_(_) / / <_  /__/_(_/|_\/ <__</_/_)_