On Sat, January 21, 2017 11:54 pm, I previously wrote:
> https://github.com/z505/fpcRun
>
>
> Project started on github. Tested to work on Windows.
>
>
> Now I just have to try Unix, as, executeprocess works slightly different
> on that system and some absolute path configuration to fpc might be ne
On Mon, January 16, 2017 1:21 pm, Lars wrote:
..
> On Mon, January 16, 2017 3:59 am, Sven Barth wrote:
>> No, FPC is a compiler, not a "runner" or debugger. That would even be
>> one of the few points where patches would *not* be welcome.
>>
>
> fpcrun.exe is an alternative to "fpc run"
>
> fpcrun.
On Mon, 16 Jan 2017 13:15:40 -0700
"Lars" wrote:
>[...]
> Does instantfpc make it mandatory that you put this at the top of every
> source file:
> > #!/usr/local/bin/fpc.d/3.0.0/instantfpc --set-cache=./
No.
That's only needed if you want to run the Pascal file directly:
./project1.pas
> f
On Mon, January 16, 2017 3:59 am, Sven Barth wrote:
> Am 16.01.2017 08:07 schrieb "Lars" :
>
>>
>> Is there a way to compile a program with fpc at the command line and
>> run it right after?
>>
>> Something like
>> fpc run project1.pas -Fu../
>
> No, FPC is a compiler, not a "runner" or debugger. T
On Mon, January 16, 2017 6:59 am, Mark Morgan Lloyd wrote:
> On 16/01/17 13:30, Mattias Gaertner wrote:
>
>> On Mon, 16 Jan 2017 05:22:14 -0700
>> "Lars" wrote:
>>
>>
>>> [...]
>>> That instantfpc has catch22 like you cant compule multiple projects
>>> with the same name, i.e. it caches file name
On 16/01/17 13:30, Mattias Gaertner wrote:
On Mon, 16 Jan 2017 05:22:14 -0700
"Lars" wrote:
[...]
That instantfpc has catch22 like you cant compule multiple projects with
the same name, i.e. it caches file name only (caveat) whereas fpcrun would
compile it in current directory, as normal, no s
On Mon, 16 Jan 2017 05:22:14 -0700
"Lars" wrote:
>[...]
> That instantfpc has catch22 like you cant compule multiple projects with
> the same name, i.e. it caches file name only (caveat) whereas fpcrun would
> compile it in current directory, as normal, no special cache dir needed
Feel free to a
On Mon, January 16, 2017 3:08 am, Mattias Gaertner wrote:
> On Mon, 16 Jan 2017 00:06:59 -0700
> "Lars" wrote:
>
>
>> Is there a way to compile a program with fpc at the command line and
>> run it right after?
>>
>> Something like
>> fpc run project1.pas -Fu../
>
> instantfpc -Fu../ project1.pas
>
Am 16.01.2017 08:07 schrieb "Lars" :
>
> Is there a way to compile a program with fpc at the command line and run
> it right after?
>
> Something like
> fpc run project1.pas -Fu../
No, FPC is a compiler, not a "runner" or debugger. That would even be one
of the few points where patches would *no
On Mon, 16 Jan 2017 00:06:59 -0700
"Lars" wrote:
> Is there a way to compile a program with fpc at the command line and run
> it right after?
>
> Something like
> fpc run project1.pas -Fu../
instantfpc -Fu../ project1.pas
> The only thing I could find was InstantFpc, which may serve simila
On Mon, January 16, 2017 2:55 am, Graeme Geldenhuys wrote:
> On 2017-01-16 07:06, Lars wrote:
>
>> The only thing I could find was InstantFpc, which may serve similar
>> purpose but not really the same as what I was thinking...
>
> If InstantFPC doesn't work for you, you could always compile the FP
On 2017-01-16 07:06, Lars wrote:
> The only thing I could find was InstantFpc, which may serve similar
> purpose but not really the same as what I was thinking...
If InstantFPC doesn't work for you, you could always compile the FPC
Compiler into your "own" executable that does compilation and then
Is there a way to compile a program with fpc at the command line and run
it right after?
Something like
fpc run project1.pas -Fu../
The only thing I could find was InstantFpc, which may serve similar
purpose but not really the same as what I was thinking...
For some reason (I may remember inco
13 matches
Mail list logo
