You could still tell Xcode how much farther back you want to be able to
build for. I think that is reasonable. You could also argue that this only
matters if someone does a build to be redistributed in binary form and then
they should decide which OS releases they want their binary to work on.

On Thursday, November 1, 2012, Sean McBride wrote:

> On Thu, 1 Nov 2012 09:19:38 +0100, Ludovic Rousseau said:
>
> >I mostly agree. But: :-)
> >- the default is then to build a 32-bits library on my 64-bits system.
> >I don't know why.
> >- ??Xiaofan complained that only one architecture was targeted.
>
> The current configure script also builds for only one architecture.
>
> >I don't know if we can have the same Xcode project for every versions
> >of Mac OS X the project wants to support.
> >I would just support the latest version of OS X and as much as
> >possible of older versions. If support of PowerPC is too complex then
> >drop it (by default) and document how to enable it.
> >I have no problem if someone else wants to support older versions of
> >Xcode and/or Mac OS X.
>
> PowerPC is supported by libusbx already, both by the code and configure
> script.  Removing support just because of Xcode is crazy, especially since
> the whole need for Xcode is only when building from git.
>
> With today's configure script, the user still has to do some setup if he
> wants a specific compiler, specific architectures, SDK, deployment targets,
> etc.  I have seen in many open source projects in the past where they meant
> well and set a specific SDK version or compiler version in their Xcode
> project.  Then a few releases later, the gcc 4.2 compiler and 10.5 SDK are
> gone and the project won't build.  The only sensible thing, for both
> forward and backward compatibility, is to let Xcode pick its default
> compiler, default SDK, default architecture, and default deployment target.
>  Notice that's also how the configure script works today!  Nowhere in there
> is it forced to build x86_64 instead of i386, etc.
>
> I agree its weird that today's Xcode seems to build 32 by default even on
> a 64 bit system, but that probably won't be true in future Xcodes.
>
> How about we add some instructions and a place to specify custom values,
> like this:
>
> <
> https://github.com/seanm/libusbx/commit/662e2e4ecb64c206ac4b5239dcf8d00959428ea1
> >
>
> Cheers,
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng                 s...@rogue-research.com<javascript:;>
> Rogue Research                        www.rogue-research.com
> Mac Software Developer              Montréal, Québec, Canada
>
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> libusbx-devel mailing list
> libusbx-devel@lists.sourceforge.net <javascript:;>
> https://lists.sourceforge.net/lists/listinfo/libusbx-devel
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

Reply via email to