librelist archives

« back to archive

How to build things with weird directory layouts?

How to build things with weird directory layouts?

From:
John Harrison
Date:
2011-11-05 @ 18:28
Homebrew Users,

I have been trying to figure out how to build a package (MAME) on OS X
Lion, but the package has few oddities about it.
http://mamedev.org/release.html is where you can download the source if
your interested in looking at this. For whatever reason, they choose to zip
the source twice. Which means, after the first unzip there is still a zip
file left over. There is also no configure script, just a makefile. It
works, you can get it to build on OS X (I tested Lion, but it should work
on previous versions of OS X), but it doesn't have a 'bin' folder or a make
'install' operation.

So... is there a common strategy for installing things that don't have an
'install' operation or a 'traditional' layout?

-- 
John Harrison

Re: [homebrew] How to build things with weird directory layouts?

From:
Misty De Meo
Date:
2011-11-05 @ 18:34
I tried to formula up MAME awhile ago but gave up for my sanity.
You're braver than I am. ;) How did you get SDL to work with the
Homebrew-provided SDL?

You can use the #install method to install files into the standard
prefix, such as `bin.install 'mame'`. There are variables for various
standard directories listed in the Formula Cookbook.

Misty

On Sat, Nov 5, 2011 at 1:28 PM, John Harrison <ash.gti@gmail.com> wrote:
> Homebrew Users,
> I have been trying to figure out how to build a package (MAME) on OS X Lion,
> but the package has few oddities about it. http://mamedev.org/release.html
> is where you can download the source if your interested in looking at this.
> For whatever reason, they choose to zip the source twice. Which means, after
> the first unzip there is still a zip file left over. There is also no
> configure script, just a makefile. It works, you can get it to build on OS X
> (I tested Lion, but it should work on previous versions of OS X), but it
> doesn't have a 'bin' folder or a make 'install' operation.
> So... is there a common strategy for installing things that don't have an
> 'install' operation or a 'traditional' layout?
>
> --
> John Harrison
>