search

salah1979 / iphone-dev

Automatically exported from code.google.com/p/iphone-dev
0 stars 0 forks source link

install-headers.sh not handling spaces in 'with-macosx-headers=' directory #97

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Put SDK in a directory containing a space
2. Use configure --with-macosx-headers=/directory/to my/sdk
3. execute install-headers.sh

What is the expected output? What do you see instead?

I expected it to work, and it didn't--at least not completely.  Parts of
the script die when there are spaces in the directory.

What version of the product are you using? On what operating system?

On linux/slackware, latest svn.

Please provide any additional information below.
It's not a big deal, and is an easy fix.  Because the apple website only
seems to let you download the 3.0 xcode, and I needed the 2.4.1, I had to
torrent it.  The result was that the path had a space and broke the
script--although it seemed to work so I spent way too much time
copying/patching things by hand.. sigh. Works now though :)

Original issue reported on code.google.com by will...@gmail.com on 2 Nov 2007 at 3:32

GoogleCodeExporter commented 8 years ago 
The documentation clearly states that spaces are not allowed in directory 
names. 
This is a known issue with almost everything that would be compiled with GCC.  
Its
unlikely this will be considered a defect by anyone who is familiar with Unix.  

If you really insist on having spaces, you will have to modify the entire build
process which is probably far too much effort to be worthwhile.  Just give in 
an put
an underscore to replace that space in the directory name.

Original comment by spect...@gmail.com on 19 Dec 2007 at 10:23

GoogleCodeExporter commented 8 years ago 
It's not about me being unfamiliar or 'giving in', but thanks for the thought.  
As I
mentioned the space was an accidental result of torrenting, and caused 
problems. 
Close it-- I've long since compiled the toolchain, just thought that you might 
want
to be aware of this issue (and document it).  Apparently you are (and 
apparently it's
documented, which I missed, my mistake) so objective achieved.
Thanks. :)

Original comment by will...@gmail.com on 19 Dec 2007 at 10:32