On Thu, 30 Aug 2007, Graeme Geldenhuys wrote:
> On 30/08/2007, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> >
> > User's manual, section 5.3 "Variable substitution in paths".
> >
>
>
> That obvious!! ;-) Thanks Michael. It works perfectly now.
>
> PS:
> Not sure if I told you, but tiOPF
On 30/08/2007, Jonas Maebe <[EMAIL PROTECTED]> wrote:
>
> Using custom fpc config files has its own issues, see
> http://www.freepascal.org/mantis/view.php?id=9450
>
> The config file handling was simply not designed with this purpose in
> mind. fpcmake really is quite easy to use.
Funny that. It
On 30 Aug 2007, at 14:11, Graeme Geldenhuys wrote:
Ummm... damn. I was hoping to get away from Makefile's (for CLI
users) and instead use a custom extrafpc.cfg file in each of the
important directories. I guess it's back to reading the manual on
Makefile.fpc and fpcmake.
Using custom fpc co
On 30/08/2007, Jonas Maebe <[EMAIL PROTECTED]> wrote:
>
> I guess you mean -FU...
Ah yes. That's what I meant.
> > How can I force the compiler to create the output directory if it
> > doesn't exist? Is there another parameter for that?
>
> No, the compiler does not create directories, only file
On 30 Aug 2007, at 13:59, Graeme Geldenhuys wrote:
I now specify a unit output path as follows:
-Fu../lib/$fpctarget
I guess you mean -FU...
How can I force the compiler to create the output directory if it
doesn't exist? Is there another parameter for that?
No, the compiler does no
On 30/08/2007, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> >
>
> User's manual, section 5.3 "Variable substitution in paths".
>
Another question... (sorry). I read the whole chapter 5 and looked at
the fpc parameters and couldn't find any hints.
I now specify a unit output path as follows:
On 30/08/2007, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
>
> User's manual, section 5.3 "Variable substitution in paths".
>
That obvious!! ;-) Thanks Michael. It works perfectly now.
PS:
Not sure if I told you, but tiOPF Core is now GUI free! At last true
non-gui apps can be written. I've
On Thu, 30 Aug 2007, Graeme Geldenhuys wrote:
> Hi,
>
> Under Lazarus I can specify the unit output directory as follows:
> ../../lib/$(TargetCPU)-$(TargetOS)
>
>
> I'm trying to do the same thing from the command line (without
> Lazarus), but FPC doesn't know about the TargetCPU or TargetO
Hi,
Under Lazarus I can specify the unit output directory as follows:
../../lib/$(TargetCPU)-$(TargetOS)
I'm trying to do the same thing from the command line (without
Lazarus), but FPC doesn't know about the TargetCPU or TargetOS macros.
Is there something else or similar I can use in my cus
