[fpc-devel] The future of fpmake

[Michael Van Canneyt]

On Wed, 30 Mar 2011, Darius Blaszyk wrote:

>
> On Mar 30, 2011, at 9:12 PM, Michael Van Canneyt wrote:
>>>>>>> - execute fpmake from command line (see thread by mattias : "run
>>>>>>> pascal programs as script") for this we would need instantfpc to
>>>>>>> support win32 and it should be supplied as a standard fpc tool
>>>>>>
>>>>>> I doubt this is feasible for windows. As far as I know, no #! comparable
>>>>>> construct exists.
>>>>>
>>>>> It is extension dependend on windows: typing just test.pp starts lazarus
>>>>> on my windows.
>>>>
>>>> So it does here, but I doubt this is what we want ? :-)
>>>
>>> It's not. A possible workaround is to use a distinct extension for makefiles and assign this extension to instantfpc.
>>
>> 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 ?

>
>> (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 ?

Michael.