[fpc-devel] The future of fpmake

Michael Van Canneyt michael at freepascal.org
Thu Mar 31 00:06:58 CEST 2011



On Wed, 30 Mar 2011, Darius Blaszyk wrote:

>
> On Mar 30, 2011, at 9:37 PM, Michael Van Canneyt wrote:
>
>>>> I don't think this is needed/wanted. fpmake.pp is intended to be used in tandem with fppkg, and that looks for a fpmake.pp program, not a script.
>>> For FPC yes, but for standalone projects this is not the case as you mentioned. Apart from that I don't see an issue even for fppkg, other than the fact that the extension might be hardcoded, which could be modified. Please note that I'm for a more holistic approach for fpmake.
>>
>> Which means ?
> Which means that 1) when using fpmake outside FPC we can do whatever we want 
> (provided we do not run into a wall because of a hardcoded extension somewhere). 
> 2) even for FPC I see no objective argument not to change the extension.
>>>
>>>> (not to mention all the possible complications on Windows, probably Mac OS as well)
>>> Can you name a potential issue you see by renaming the makefile to some other extension? I thought that FPC does not mind which extension you use, as long as the syntax is correct?
>>
>> It does not mind.
>>
>> Well, if you don't intend to use it for FPC, you can do all you want;
>> you don't need our permission for that ?
>
> I was not asking permission or did I? It was you who stated that there were complications. 
> I just asked to name one. Don't get me wrong, there might be some, but I fail to see which.

But I didn't claim to know all possible complications. I just meant to say that are possibly catches
which we currently don't know about; so jumping on a system that relies on the "instantfpc" trick 
for all platforms may be a bit premature. The thing is barely a week old :-)

That said:
Obviously, you can give your fpmake script/program any extension you want for your 'outside fpc' 
projects, associate whatever you want with it on all platforms you see fit.

But since fppkg is for the express (and only) purpose of installing FPC code packages, 
I see nothing wrong with requiring .pas or .pp as an extension for the fpmake file if 
it is to be used with fppkg.

Michael.



More information about the fpc-devel mailing list