Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


On Mon, Oct 04, 2010 at 08:44:08PM -0700, Joseph Powers wrote:
{
         print "Setting values for Mac OS X/Darwin on x86... ";
         $outfile        = "MacOSXX86Env.Set"; 
         $CPU            = "I";
         $CPUNAME        = "INTEL";
         $OUTPATH        = "unxmacxi";
}

which imho is broken, sorry. (Unless you make it build 32bit binaries).
Unless you do something special I think it'll create 64bit binaries...

Actually this works too well. It's placing a -cpu i386 on everything (I'm assuming that because Mac 
supports two CPUs, they placed -cpu on everything already)... For Macs this should be something 
like i686 since we don't have i386 Macs.

I believe that we might need to change it to something like the following if we ever want to 
support a 64bit build on Mac:
{
         print "Setting values for Mac OS X/Darwin on x86... ";
         $outfile        = "MacOSXX86_64Env.Set"; 
         $CPU            = "X";
         $CPUNAME        = "X86_64";
         $OUTPATH        = "unxmacxx";
}

Correct.

However, I don't think the rest of the build system would handle that very well.

Yeah, I guess you need adaptions here and there as well (e.g. in solenv and
stuff checking for $OS and $CPUNAME.

64bit Aqua only runs on 10.5+ and management wants to keep the build 10.4 friendly (plus I just 
want to get anything built and running now).

Gr??e/Regards,

Ren?


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.