Makefile-engine broken on Haiku PM

[kallisti5]

• Copy the makefile from /boot/common/develop/etc/ to a project
• Make adjustments to the makefile
• Run make, get: No fule to make target '/boot/system/develop/etc/makefile-engine'

While I agree makefile-engine should be in system... that is going to break a lot of legacy stuff. (or we need to just update the template to reflect the new location)

[kallisti5]

it actually looks like $BUILDHOME doesn't agree with the location of the makefile-engine and template. Not sure what the intended path was on PM.. so i'm not going to touch this one.

[bonefish]

The BUILDHOME variable is kind of obsolete. IIRC it only exits because some legacy applications use it. Haiku itself doesn't and given that development files can be installed in three different locations, it might not work as expected anyway.

A path to the makefile engine that remains stable regardless of where it is installed, would be "/packages/makefile_engine-*/.self/develop/etc/makefile-engine". If multiple versions of the makefile engine package are installed, there will be multiple matching entries in "/packages/". One (the latest?) would need to be chosen.

[siarzhuk]

Hm... in hrev46263 my old makefile-engine driven projects were rebuilded successfully. Fixed?

[bonefish]

As a side effect of removing "/boot/common" the makefile-engine is back in "/boot/system/develop/etc". The makefile should still be adjusted to refer to the "/packages/makefile_engine..." path, though.

[bonefish]

hrev46402 adjusts the template makefile to find makefile-engine regardless of the package's installation location.