Re: ar.exe & scripts

Brian Dessent wrote:
> Florian Schricker wrote:
>
>
> > the lib is actually created with no problems. This also shows that the
> > above error has nothing to do with permissions as ar can create the lib
> > in the correct place, but only using a relative path. Now that's what I
> > call odd! :-/
>
>
> Why is that odd?  'ar' is a mingw application and it must be given win32
> paths.  "c:/path" ought to work but "/c/path" will not unless you
> actually mean a subdirectory "/c" in the root of the current drive.
>
> Remember that the whole point of MSYS is to do this path translation for
> mingw apps, but since 'ar' is reading this file directly there is no way
> for this translation to happen.  So any path you give it must be a valid
> win32 path.


Thanks for clearing this up - as said I am still new to MinGW/MSYS and 
it seems as if I just got carried away by "woot I finally have a shell 
I'm so much used to". :-/
I am/was still reading up on all this stuff...

I figured that, if I'd used *correct* absoulte or relative paths in 
these ar-scripts I'll get along - but this is unlikely to happen; I 
guess I'll look around for better ways of using qmake (and these 
project-files) - but thanks again to you and Greg Chicares for the 
effort and enlightenment!


regards,
Florian Schricker


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click