Am 14.09.2015 um 12:29 schröbte Gary V. Vaughan: > Hi, Hi!
> > Yes, setting MACOSX_DEPLOYMENT_TARGET is a good idea, or else the resulting > library > *may* depend on system library symbols not available in releases prior to the > one you > compile on. > > There's no need to split it into two commands though: > > CC='env MACOSX_DEPLOYMENT_TARGET=10.5 gcc' > > has served me well over the years. There is also a gcc command line switch[1] that presumably does the same. > > Another option might be to not support binary distribution, so the > environment setting > then becomes unnecessary, because the end user will presumably be compiling > your > module on the machine that will use it, and so compatibility with previous OS > releases > is not needed. +1 on that, because a binding/library might depend on a different setting than what LuaRocks assumes. Why forbid bindings that use the newest features Apple has to offer?! If binary distribution is intended, the uploader of the binary rock should set a suitable deployment target before compiling/packing. > > Cheers, > Philipp [1]: https://github.com/keplerproject/luarocks/pull/281 ------------------------------------------------------------------------------ _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
