Re: Mplayer Variant Help
Thanks for the detailed response. I don't know enough about compiling to come up with a universal build, so I guess I'll stick with an intel only build. If I may, I have a follow up on the platform constraints. So these constraints have nothing to do with what systems the compiled binaries will run on. Is that right? I seem to recall reading somewhere that macport builds will run on 10.4 and higher if I install with 10.5. Looking at the macports guide, it looks like if there is no configure.compiler line in the port file and if I'm using 10.5.6, then the default is gcc-4.0 which will result in 10.4 and 10.5 friendly binaries. Am understanding that correctly? Thanks. On May 13, 2009, at 7:38 PM, Ryan Schmidt wrote: On May 13, 2009, at 12:25, EmmGunn wrote: I'm looking at the different variants for mplayer and most of them are self explanatory, but I have a couple of questions. I noticed this in the port file: 83 # configure is not autoconf 84 universal_variant no which I took to mean that a universal variant is not available, That's correct. Because mplayer does not use a standard autoconf configure script, the standard universal variant does not work with it. If someone wanted to invest some time in figuring out how to make mplayer compile universal, it could probably be done by writing a custom universal variant for that port. but then I see a binary_codecs variant which has something about powerpc and i386. What does this do exactly? Is this something equivalent to a universal variant? I was hoping to compile a universal build of mplayer. Sorry, the port says universal_variant no, which means someone tried to build a universal binary and found that it failed, and added this to the portfile to save you the trouble. If you really want a universal binary, you will have to write a custom universal variant for this port. If you do, please contribute it back to us so that we can put it in the portfile. Also, just out of curiosity, what are the darwin and darwin_8 variants. I couldn't find anything about them either. Thanks in advance for any help. These are platform variants. If they are present in a portfile, MacPorts automatically selects them on the appropriate platform. darwin variants are selected on operating systems based on Darwin, including Mac OS X. darwin_8 is selected on Darwin 8.x operating systems, such as Mac OS X 10.4.x. Darwin 9.x would be Mac OS X 10.5.x, and so on. darwin_i386 is selected if you're running Darwin (or Mac OS X) on an Intel processor. darwin_powerpc is selected if you're running Darwin (or Mac OS X) on a PowerPC processor. You never select these variants manually; MacPorts does it for you if necessary. Ports use these variants if they need different instructions to build correctly in different kinds of environments. The description of the binary_codecs variant says Enable platform- specific binary codecs. Most ports in MacPorts are compiled from source but sometimes bits are only available as pre-compiled binaries, as is apparently the case for the codecs this variant wants to enable. This variant seems to be designed to download one file for PowerPC computers and a different file for Intel computers, and then install their contents. However, I don't believe the variant functions as intended. It checks whether variants darwin_i386 or darwin_powerpc are set. Since the port does not declare any variants by those names, those variants are never set, hence the binary_codecs variant never does anything. This is a bug in the portfile. It looks like when the binary_codecs variant was set up in r20652, darwin_i386 and darwin_powerpc variants did exist in the port, but they were subsequently removed without considering the effect that would have on the binary_codecs variant. I fixed this bug just now, but now the variant produces an error. Since I'm not an MPlayer expert I filed a ticket for this problem: http://trac.macports.org/ticket/19619 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Mplayer Variant Help
I couldn't get the mplayer to build and so tried mplayer-devel which worked like a charm. On May 13, 2009, at 8:35 PM, Eric Cronin wrote: On May 13, 2009, at 10:38 PM, Ryan Schmidt wrote: On May 13, 2009, at 12:25, EmmGunn wrote: I'm looking at the different variants for mplayer and most of them are self explanatory, but I have a couple of questions. I noticed this in the port file: 83 # configure is not autoconf 84 universal_variant no which I took to mean that a universal variant is not available, That's correct. Because mplayer does not use a standard autoconf configure script, the standard universal variant does not work with it. If someone wanted to invest some time in figuring out how to make mplayer compile universal, it could probably be done by writing a custom universal variant for that port. but then I see a binary_codecs variant which has something about powerpc and i386. What does this do exactly? Is this something equivalent to a universal variant? I was hoping to compile a universal build of mplayer. Sorry, the port says universal_variant no, which means someone tried to build a universal binary and found that it failed, and added this to the portfile to save you the trouble. If you really want a universal binary, you will have to write a custom universal variant for this port. If you do, please contribute it back to us so that we can put it in the portfile. If someone is interested in tackling the universal build they may want to contact Mo Haque and see if the scripts he uses to update http://haque.net/software/mplayer/mplayerosx/builds/ are useful in manually setting up the crosscompile environment. Also, I'm not sure what the state of the new port is, but if mplayer- devel builds currently I would strongly recommend it over the MPlayer port since upstream stopped rolling full releases over 2 years ago and MPlayer hasn't been updated other than to fix build issues since then. Thanks, Eric ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Mplayer Variant Help
On 2009-5-15 02:20, EmmGunn wrote: If I may, I have a follow up on the platform constraints. So these constraints have nothing to do with what systems the compiled binaries will run on. Is that right? I seem to recall reading somewhere that macport builds will run on 10.4 and higher if I install with 10.5. That's not true in general. Platform variants contain code specific both to building on the corresponding platform and to running on it. MacPorts does not currently offer a way to build on one platform and target another. Running Leopard-built binaries on Tiger may succeed in *some* cases if you change universal_target to 10.4 and universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk. But any time there is a darwin_8 and/or darwin_9 variant, MP will select the one matching the build machine, which will generally cause problems. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Mplayer Variant Help
Sorry for being so dense, but what happens when your installing using system 10.5 and there is a darwin_8 variant but no darwin_9 variant? Will the darwin_8 be used and the result work on 10.4, but then be iffy on 10.5? This is the mplayer-devel port file. On May 14, 2009, at 10:35 AM, Joshua Root wrote: On 2009-5-15 02:20, EmmGunn wrote: If I may, I have a follow up on the platform constraints. So these constraints have nothing to do with what systems the compiled binaries will run on. Is that right? I seem to recall reading somewhere that macport builds will run on 10.4 and higher if I install with 10.5. That's not true in general. Platform variants contain code specific both to building on the corresponding platform and to running on it. MacPorts does not currently offer a way to build on one platform and target another. Running Leopard-built binaries on Tiger may succeed in *some* cases if you change universal_target to 10.4 and universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk. But any time there is a darwin_8 and/or darwin_9 variant, MP will select the one matching the build machine, which will generally cause problems. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Mplayer Variant Help
On 2009-5-15 04:28, EmmGunn wrote: Sorry for being so dense, but what happens when your installing using system 10.5 and there is a darwin_8 variant but no darwin_9 variant? Will the darwin_8 be used and the result work on 10.4, but then be iffy on 10.5? This is the mplayer-devel port file. Nope, darwin_8 variants are only selected on darwin 8 (Tiger). Something built on Tiger and deployed on Leopard has a far better chance of working than the other way round, BTW. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Mplayer Variant Help
Thanks. That makes sense. On May 14, 2009, at 12:08 PM, Joshua Root wrote: On 2009-5-15 04:28, EmmGunn wrote: Sorry for being so dense, but what happens when your installing using system 10.5 and there is a darwin_8 variant but no darwin_9 variant? Will the darwin_8 be used and the result work on 10.4, but then be iffy on 10.5? This is the mplayer-devel port file. Nope, darwin_8 variants are only selected on darwin 8 (Tiger). Something built on Tiger and deployed on Leopard has a far better chance of working than the other way round, BTW. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Mplayer Variant Help
On May 13, 2009, at 12:25, EmmGunn wrote: I'm looking at the different variants for mplayer and most of them are self explanatory, but I have a couple of questions. I noticed this in the port file: 83 # configure is not autoconf 84 universal_variant no which I took to mean that a universal variant is not available, That's correct. Because mplayer does not use a standard autoconf configure script, the standard universal variant does not work with it. If someone wanted to invest some time in figuring out how to make mplayer compile universal, it could probably be done by writing a custom universal variant for that port. but then I see a binary_codecs variant which has something about powerpc and i386. What does this do exactly? Is this something equivalent to a universal variant? I was hoping to compile a universal build of mplayer. Sorry, the port says universal_variant no, which means someone tried to build a universal binary and found that it failed, and added this to the portfile to save you the trouble. If you really want a universal binary, you will have to write a custom universal variant for this port. If you do, please contribute it back to us so that we can put it in the portfile. Also, just out of curiosity, what are the darwin and darwin_8 variants. I couldn't find anything about them either. Thanks in advance for any help. These are platform variants. If they are present in a portfile, MacPorts automatically selects them on the appropriate platform. darwin variants are selected on operating systems based on Darwin, including Mac OS X. darwin_8 is selected on Darwin 8.x operating systems, such as Mac OS X 10.4.x. Darwin 9.x would be Mac OS X 10.5.x, and so on. darwin_i386 is selected if you're running Darwin (or Mac OS X) on an Intel processor. darwin_powerpc is selected if you're running Darwin (or Mac OS X) on a PowerPC processor. You never select these variants manually; MacPorts does it for you if necessary. Ports use these variants if they need different instructions to build correctly in different kinds of environments. The description of the binary_codecs variant says Enable platform- specific binary codecs. Most ports in MacPorts are compiled from source but sometimes bits are only available as pre-compiled binaries, as is apparently the case for the codecs this variant wants to enable. This variant seems to be designed to download one file for PowerPC computers and a different file for Intel computers, and then install their contents. However, I don't believe the variant functions as intended. It checks whether variants darwin_i386 or darwin_powerpc are set. Since the port does not declare any variants by those names, those variants are never set, hence the binary_codecs variant never does anything. This is a bug in the portfile. It looks like when the binary_codecs variant was set up in r20652, darwin_i386 and darwin_powerpc variants did exist in the port, but they were subsequently removed without considering the effect that would have on the binary_codecs variant. I fixed this bug just now, but now the variant produces an error. Since I'm not an MPlayer expert I filed a ticket for this problem: http://trac.macports.org/ticket/19619 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Mplayer Variant Help
On May 13, 2009, at 21:38, Ryan Schmidt wrote: Also, just out of curiosity, what are the darwin and darwin_8 variants. I couldn't find anything about them either. Thanks in advance for any help. These are platform variants. If they are present in a portfile, MacPorts automatically selects them on the appropriate platform. [snip] and they are described in the Guide, FYI: http://guide.macports.org/#reference.variants.platform ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Mplayer Variant Help
On May 13, 2009, at 10:38 PM, Ryan Schmidt wrote: On May 13, 2009, at 12:25, EmmGunn wrote: I'm looking at the different variants for mplayer and most of them are self explanatory, but I have a couple of questions. I noticed this in the port file: 83 # configure is not autoconf 84 universal_variant no which I took to mean that a universal variant is not available, That's correct. Because mplayer does not use a standard autoconf configure script, the standard universal variant does not work with it. If someone wanted to invest some time in figuring out how to make mplayer compile universal, it could probably be done by writing a custom universal variant for that port. but then I see a binary_codecs variant which has something about powerpc and i386. What does this do exactly? Is this something equivalent to a universal variant? I was hoping to compile a universal build of mplayer. Sorry, the port says universal_variant no, which means someone tried to build a universal binary and found that it failed, and added this to the portfile to save you the trouble. If you really want a universal binary, you will have to write a custom universal variant for this port. If you do, please contribute it back to us so that we can put it in the portfile. If someone is interested in tackling the universal build they may want to contact Mo Haque and see if the scripts he uses to update http://haque.net/software/mplayer/mplayerosx/builds/ are useful in manually setting up the crosscompile environment. Also, I'm not sure what the state of the new port is, but if mplayer- devel builds currently I would strongly recommend it over the MPlayer port since upstream stopped rolling full releases over 2 years ago and MPlayer hasn't been updated other than to fix build issues since then. Thanks, Eric ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Mplayer Variant Help
On May 13, 2009, at 22:35, Eric Cronin wrote: If someone is interested in tackling the universal build they may want to contact Mo Haque and see if the scripts he uses to update http://haque.net/software/mplayer/mplayerosx/builds/ are useful in manually setting up the crosscompile environment. There's also a ticket for this issue. http://trac.macports.org/ticket/17455 Also, I'm not sure what the state of the new port is, but if mplayer-devel builds currently I would strongly recommend it over the MPlayer port since upstream stopped rolling full releases over 2 years ago and MPlayer hasn't been updated other than to fix build issues since then. Yeah, their (non-)release policy is pretty stupid. I don't know what else to call it. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
