Advice for non-standard package

[Ryan Schmidt]

On Jun 4, 2011, at 17:01, Thomas Robitaille wrote:

> I'm trying to create a Portfile for a package that doesn't quite follow the standard configure ; make ; make install method for installing.
> 
> Configure isn't needed,

Ok, as you discovered you use "use_configure no" for this. This then makes you responsible for ensuring you're UsingTheRightCompiler and build arch and adding a universal variant if possible.

https://trac.macports.org/wiki/UsingTheRightCompiler


> and make install isn't defined.

Ok, as you discovered you can override the destroot phase and define it yourself as needed.


> When make is run, it actually runs configure scripts and 'make' in sub-directories. The attached Portfile does get the software to install correctly on my computer, but I don't think it's using the macports gcc compilers, and presumably this is an issue.
> 
> What is the best way to enforce the use of macports compilers in this kind of package? Should I have a patch that goes and replaces instances of compiler commands with e.g. /opt/local/bin/gcc-mp-4.4? (then add gcc44 as a dependency).

MacPorts compilers should not be used unless there is a specific reason why the version of GCC Apple supplies with Xcode will not work. If a MacPorts compiler is needed, then, assuming you've already done the work above to ensure you're UsingTheRightCompiler, you simply set "configure.compiler" to the desired value, as you would with any port.


Other comments:

The version field should be 3.3, not v3.3.