Hi,

if a Makefile.fpc is generated by lazarus from a lazarus package (.lpi file), would this Makefile.fpc be sufficient for integrating the package into the fpc package tree below the "extra" directory?

TIA,

Marc Santhoff wrote

if a Makefile.fpc is generated by lazarus from a lazarus package (.lpi file), would this Makefile.fpc be sufficient for integrating the package into the fpc package tree below the "extra" directory?

The base/extra separation has been removed for about 1.5 year now. Everything is in packages/ dir.

I don't know if the generated Makefile.fpc's are enough, I don't know what Lazarus generates.

Note that makefile.fpc is on the way out, long term, so better not spend too much time on it.

Marc Santhoff wrote

if a Makefile.fpc is generated by lazarus from a lazarus package (.lpi file), would this Makefile.fpc be sufficient for integrating the package into the fpc package tree below the "extra" directory?

There is no "extra" directory anymore since FPC 2.2.2. Anyway, some of the main requirements for adding a new package to FPC are that it doesn't have any Lazarus/LCL dependencies, and that we have a reasonable expectation that the person asking for it to be included will also maintain and update it in the future.

Jonas

If you're talking about the transition to the new pascal style make tool, I'm aware of that. I think lazarus will follow in genreating pascal make scripts.

If you want to point out the new package management I know of it, too. Are there any rough sketches of when it will be established?

I was thinking about using it for injecting local packages into the pascal tree to make system admin life easier. This way there would be only one location where pascal library like stuff is to put and remember.

If there is something to be published to the world I'd certainly ask if it is of any use for others beforhand.