What you want is FPMake, not FPCMake. FPCMake is just a generator of GNU
makefiles. As Michael said elsewhere though, FPMake is an API designed
specifically for compiling FPC programs, basically. You write a program
using the API, put it in a file that should always be called "fpmake.pp",
and then
> On Sep 1, 2020, at 9:04 PM, Tony Whyman via fpc-pascal
> wrote:
>
> My primary motivation for going with fpcmake is that it is a very good fit
> with the debian package management system (and rpmbuild). My normal build
> target is Ubuntu and hence I want to generate .deb files in order to
On 01/09/2020 14:29, Ryan Joseph via fpc-pascal wrote:
On Sep 1, 2020, at 7:46 PM, Tony Whyman via fpc-pascal
wrote:
fpcmake is a pre-processor that generates makefiles for fpc projects. You can
use it to do just about anything a standard makefile can do, including
including resource file
On 2020-09-01 15:29, Ryan Joseph via fpc-pascal wrote:
On Sep 1, 2020, at 7:46 PM, Tony Whyman via fpc-pascal
wrote:
fpcmake is a pre-processor that generates makefiles for fpc projects.
You can use it to do just about anything a standard makefile can do,
including including resource files a
> On Sep 1, 2020, at 7:46 PM, Tony Whyman via fpc-pascal
> wrote:
>
> fpcmake is a pre-processor that generates makefiles for fpc projects. You can
> use it to do just about anything a standard makefile can do, including
> including resource files and running scripts. I use it all the time f
fpcmake is a pre-processor that generates makefiles for fpc projects.
You can use it to do just about anything a standard makefile can do,
including including resource files and running scripts. I use it all the
time for building production versions of lazarus programs and prior to
packaging th
On Tue, 1 Sep 2020, Ryan Joseph via fpc-pascal wrote:
I've never used fpcmake before and instead relied on my own custom build system
solutions which are a pain to maintain and non-standard which it makes extra
work configuring the pascal language server I'm using now.
My first question of
I've never used fpcmake before and instead relied on my own custom build system
solutions which are a pain to maintain and non-standard which it makes extra
work configuring the pascal language server I'm using now.
My first question of fpcmake is, can I package application bundles and copy
res
On Wed, May 6, 2020 at 8:03 AM Sven Barth via fpc-pascal
wrote:
> Not in the makefile.fpc,
That is unfortunate.
> but fpcmake allows you to pass a list of supported targets (usually -Tall is
> used to allow all targets), but you'd need to pick each one. This does mean
> however that everyone
Bart via fpc-pascal schrieb am Mi., 6.
Mai 2020, 02:33:
> Hi,
>
> Here's the first line of the Lazarus Makefile:
> -
> #
> # Don't edit, this file is generated by FPCMake Version 2.0.0
> #
> default: all
> MAKEFILETARGETS=i386-linux i386-go32v2 i386-win32 i
On Tue, 5 May 2020, Bart via fpc-pascal wrote:
Hi,
Here's the first line of the Lazarus Makefile:
-
#
# Don't edit, this file is generated by FPCMake Version 2.0.0
#
default: all
MAKEFILETARGETS=i386-linux i386-go32v2 i386-win32 i386-os2
i386-freebsd i3
Hi,
Here's the first line of the Lazarus Makefile:
-
#
# Don't edit, this file is generated by FPCMake Version 2.0.0
#
default: all
MAKEFILETARGETS=i386-linux i386-go32v2 i386-win32 i386-os2
i386-freebsd i386-beos i386-haiku i386-netbsd i386-solaris
i386-net
On 28 Jan 2011, at 04:17, Timothy Groves wrote:
Any attempt to invoke fpcmake results in the following error:
Processing Makefile.fpc
Error: Target "linux", package "rtl" not found
fpcmake requires the FPC sources to be installed, and the environment
variable "FPCDIR" to be set so it point
Any attempt to invoke fpcmake results in the following error:
Processing Makefile.fpc
Error: Target "linux", package "rtl" not found
The system is an HP xw8200 (stock configuration) running Ubuntu 10.10
64-bit. I have both the i386 and the x86_64 versions of fpc-2.4.2
installed on this machin
On Thu, December 10, 2009 01:03, Roland Schaefer wrote:
> Hi, do the standard targets set up by fpcmake come with any defines
> which allow conditional compilation depending on the target (like extra
> code to be compiled only when doing 'make debug', for example)? If not,
> can I get fpcmake to in
Hi, do the standard targets set up by fpcmake come with any defines
which allow conditional compilation depending on the target (like extra
code to be compiled only when doing 'make debug', for example)? If not,
can I get fpcmake to insert defines for such symbols into the generated
Makefile someho
Am Mittwoch, den 08.08.2007, 07:59 +0200 schrieb Peter Vreman:
> > Running the zipinstall and zipsourceinstall targets give me files with
> > the unchanged standard name. The final goal would be to have a name
> > formed like
> >
> > $(PACKAGE_NAME)-$(PACKAGE_VERSION).tar.gz
> >
> > for distri
> Hi again,
>
> how can the name of the files created by the targets "zipinstall" and
> "zipsourceinstall" be influenced?
>
> I've tried this way:
>
>
> [prerules]
> pretest:
> echo $(ZIPNAME)
> echo $(ZIP_ZIPNAME)
>
> [target]
> programs=cnfdat2h5
>
> [package]
> name=cnfdat2h5
> vers
Hi again,
how can the name of the files created by the targets "zipinstall" and
"zipsourceinstall" be influenced?
I've tried this way:
[prerules]
pretest:
echo $(ZIPNAME)
echo $(ZIP_ZIPNAME)
[target]
programs=cnfdat2h5
[package]
name=cnfdat2h5
version=0.1
[compiler]
options=-
Thanks Darius & Peter.
I took your advice Darius, and just tried it, and it works Using
the dirs_ looks more simplified and easier to read than the
variable method. Well, for me at least - and I only needed it in one
place.
Is the FPC Programmer's Manual somewhere in SubVersion, so I could
u
> Is the following allowed in a Makefile.fpc
>
> [target]
> units=unit1 unit2 unit3
> dirs_linux=x11
> dirs_freebsd=x11
> dirs_win32=win32
>
> I have read the docs and know the "dirs" is a valid setting in the
> "target" section. But I have seen somewhere an example where they
> included the plat
To: "FPC-Pascal users discussions"
Sent: Tuesday, August 29, 2006 3:53 PM
Subject: [fpc-pascal] fpcmake question
Is the following allowed in a Makefile.fpc
[target]
units=unit1 unit2 unit3
dirs_linux=x11
dirs_freebsd=x11
dirs_win32=win32
I have read the docs and know the "dirs" i
Is the following allowed in a Makefile.fpc
[target]
units=unit1 unit2 unit3
dirs_linux=x11
dirs_freebsd=x11
dirs_win32=win32
I have read the docs and know the "dirs" is a valid setting in the
"target" section. But I have seen somewhere an example where they
included the platform as well in the
I only went with what I found in the FPC documentation. I am very new
to FPCMake as well.
Regards,
Graeme.
On 7/28/06, Darius Blaszijk <[EMAIL PROTECTED]> wrote:
Is there somewhere a description on how to use environment variables in
FPCMake? I've been searching the programmers manual, but n
IL PROTECTED]>
To: "FPC-Pascal users discussions"
Sent: Friday, July 28, 2006 9:24 AM
Subject: [fpc-pascal] fpcmake questions
I have two questions regarding FPCMake.
1. Whe I do an FPCMake I get the following error;
Processing Makefile.fpc
Error: Target "win32", package &q
Thanks, Graeme. That did the trick
Darius
- Original Message -
From: "Graeme Geldenhuys" <[EMAIL PROTECTED]>
To: "FPC-Pascal users discussions"
Sent: Friday, July 28, 2006 9:45 AM
Subject: Re: [fpc-pascal] fpcmake questions
Hi Darius,
I had the same iss
Hi Darius,
I had the same issue ... Is my emails on the 9th July in FPC-Devel
mailing list. Titled "fpcmake keeps failing".
I had the FPCDIR set wrong... It must point to the fpc source
directory and not the fpc root directory..
export FPC=/opt/fpc-2.1.1/bin/ppc386
export FPCDIR=/opt/fpc-2.1.1
I have two questions regarding
FPCMake.
1. Whe I do an FPCMake I get the following
error;
Processing Makefile.fpcError: Target "win32",
package "rtl" not found
What is causing this error, what does it
mean?
2. I'm using the LCL in my application and I need
to enter it as a unitdir
In MS Windows, fpcmake says:
Error: Target "win32", package "libasync" not found
In my 2.1.0 source directories, libasync appears to be for unix only..i.e. it's
in a "unix" directory. Is there a libasync for windows, that fpcmake relies on?
Lars
___
f
Am Mi, den 03.03.2004 schrieb Marco van de Voort um 23:34:
> > Am Mi, den 03.03.2004 schrieb Peter Vreman um 12:46:
> > > >
> > > > Sorry for that, but it leads to the question: Does fpc do this by design
> > > > or can I switch it off?
> > >
> > > Try 1.9.x
> >
> > I'll do that later on, for now
> Am Mi, den 03.03.2004 schrieb Peter Vreman um 12:46:
> > >
> > > Sorry for that, but it leads to the question: Does fpc do this by design
> > > or can I switch it off?
> >
> > Try 1.9.x
>
> I'll do that later on, for now I need a stable set of tools
1.9.x is more stable than 1.0.x in many ways
Am Mi, den 03.03.2004 schrieb Peter Vreman um 12:46:
> > You're right. The problem is in fact the compiler. All names are changed
> > to lower case by fpc (1.0.10/FreeBSD).
> >
> > Sorry for that, but it leads to the question: Does fpc do this by design
> > or can I switch it off?
>
> Try 1.9.x
> Am Mi, den 03.03.2004 schrieb Peter Vreman um 08:03:
>> > Hi again!
>> >
>> > Apparently fpcmake has no idea of handling file names with capitals in
>> > them. I use those names for having better readability and sorting
>> > issues.
>> >
>> > When the target clean is used, none of the files with
Am Mi, den 03.03.2004 schrieb Peter Vreman um 08:03:
> > Hi again!
> >
> > Apparently fpcmake has no idea of handling file names with capitals in
> > them. I use those names for having better readability and sorting
> > issues.
> >
> > When the target clean is used, none of the files with capitals
> Hi again!
>
> Apparently fpcmake has no idea of handling file names with capitals in
> them. I use those names for having better readability and sorting
> issues.
>
> When the target clean is used, none of the files with capitals is
> deleted (.ppu, .o).
>
> I know how to write my own clean targe
Hi again!
Apparently fpcmake has no idea of handling file names with capitals in
them. I use those names for having better readability and sorting
issues.
When the target clean is used, none of the files with capitals is
deleted (.ppu, .o).
I know how to write my own clean target, but maybe ther
> Thanks Micheal & Peter, I kinda figured that was the case.
> I think I'll just move it to a sub-directory like you suggested
> peter because I'd rather not have to re-edit the raw Makefile
> every time I generate it.
re-edit Makefile is not necessary. You can add it also to Makefile.fpc
under t
Thanks Micheal & Peter, I kinda figured that was the case.
I think I'll just move it to a sub-directory like you suggested
peter because I'd rather not have to re-edit the raw Makefile
every time I generate it.
Thanks again!
This newsboard is part of what makes FPC so damn great!
All of you guys
On Tue, 24 Feb 2004, Jon D. Sawyer wrote:
> Is there a way to get FPC Make to enter its target DIRS before compiling
> the units in the current directory?
>
> I've got a unit that depends on another unit being compiled first that
> is in a sub-directory, even though I list the dirs first Make t
> Is there a way to get FPC Make to enter its target DIRS before compiling
> the units in the current directory?
>
> I've got a unit that depends on another unit being compiled first that
> is in a sub-directory, even though I list the dirs first Make trys to
> compile the current dir first.
There
Is there a way to get FPC Make to enter its target DIRS before compiling
the units in the current directory?
I've got a unit that depends on another unit being compiled first that
is in a sub-directory, even though I list the dirs first Make trys to
compile the current dir first.
Thx.. ^_^
41 matches
Mail list logo
