Re: [pupnp-devel] Xcode project and autoconf

[Marcelo J. <mar...@gm...>]

Hi Ingo,

On Thu, Jul 24, 2008 at 3:24 AM, Ingo Hofmann
<ing...@ii...> wrote:
>
> I think I expressed myself a little misleading, I'm neither a Windows
> developer nor am I using Visual Studio. I'm currently developing on
> Mac OS X, mainly using the typical autoconf approach, which works fine
> on OS X due to it's BSD underpinnings.
> What I will be trying to do in the future, is porting my software,
> which relies on pupnp, to the iPhone. The problem is now, that I would
> have to give the correct cross-compile switches to autoconf. An easier
> approach would be to simple use Xcode, which is Apples native
> development enviroment, and let it take care of the correct byte-code.
> By browsing the source-tree, I found some Windows VS files and thought
> that they were still maintained and would be a good template for
> creating an Xcode project. By fiddling around with those I found this
> pre-generated autoconfig.h and also found the above mentioned
> version ... this was the point when I started wondering and decided to
> post to the developers list :)
> So do I get you right, the Windows project are currently not
> maintained and should not be used as examples (mainly because of the
> obsolte autoconfig.h)?

Recently, Charles Nepveu has put IPv6 into libupnp. I know he tested
it on windows too, so, there is a good chance that the current
subversion repository code compiles. I say a good chance because I
might have broken it with my commits.

The file "autoconfig.h" is beeing distributed in the "build" directory
of the tarball. Originally, this file is built with the aid of the
"configure" script, based on the template file "autoconfig.h.in". But
some systems do not have conditions to run "configure", so on these
systems, the file "autoconfig.h" cannot be produced. Windows systems
usually fall into this category, but Mac OS X does not.

The file "build/autoconfig.h" is provided as it is as a way for those
poor men that have to compile the library on a system that is not able
to run "configure". You should probably edit it to fit your systems
needs, once "configure" will not do it for you.

Another option is to cross-compile. In that case, if your system is
supported by gcc, the configure script should probably handle all the
stuff. Just do

./configure --host=your-host-goes-here [other options go here]

You should find out (google?) what is the proper string for your host,
and you must have a cross-compiler tool chain for your host too. That
should probably be the good option to you, unless you want to compile
it in the iPod using gcc :)

>>> If the Xcode project turns out to be working stable, are you
>>> interested in incorporating it into the respository?
>>
>> I don't know enough about Xcode, if you can provide me some more
>> information/pointers, I can answer your question. What exactly would
>> you like to include in the libupnp distribution?
>>
>> The way I see things on the windows front is the following: we cannot
>> add support to compile on win32 unless someone is willing to maintain
>> it. And if the infrastructure does not compromise the Unix
>> infrastructure, I see no problem in including it, even if it gets
>> outdated, see for example the build/ directory.
>
> Xcode has nothing to do with Windows, see above :) I finally managed
> to get a working Xcode project on Mac OS X 10.5, but it's untested and
> uses the 1.4.7 version of autoconfig.h. Moreover, the goal was to be
> able to port pupnp to the iPhone, because I think that device would
> make up a great control point device. That means, that autoconfig.h
> gets even more voodoo, since iPhone uses e.g. arm6 CPUs.
> I think the best solution would be to read some autoconf manuals,
> start a configuration for cross-compiling and using the generated
> autoconfig.h. This will also make it possible to create pupnp the
> usual way, using the command line and make, and the link the the
> resulting libs to the according application. I will look into that as
> soon as I find some time to work on upnp again, if you are interested.

As I said before, there should be no problem if gcc supports arm6. I
have done some arm cross-compiling (actually a strongarm device) in
the past and had no trouble with that.

Ok, now I remember about Xcode. I have never used it because I lack a
Mac :( but I surely have heard about it.

My position is that if you want to include configuration files for the
Xcode environment, the same way we do today for MSVC8 and MSVC9, they
will surely be accepted. They have a place in "buid/xcode", I can
create the directory anytime you want.

> Thanks for your clarifications and best regards,
> Ingo

You are welcome.

Regards,
Marcelo.