On Fri, 10 Aug 2007, Darius Blaszijk wrote:
> Johann Glaser wrote:
> > Is there any documentation (like the things you've written in this
> > thread) in the Wiki? If not, I'd like to copy-paste (and clean up) your
> > discussion. Please point me to a place where the information best fits.
> >
Johann Glaser wrote:
Is there any documentation (like the things you've written in this
thread) in the Wiki? If not, I'd like to copy-paste (and clean up) your
discussion. Please point me to a place where the information best fits.
I was also thinking the same ;) . I've created a stub here:
h
Hi!
Am Freitag, den 10.08.2007, 15:24 +0200 schrieb Michael Van Canneyt:
>
> On Fri, 10 Aug 2007, Graeme Geldenhuys wrote:
>
> > On 10/08/07, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> > >
> > > It's super configurable.
> > >
> > > ./fpmake --help
> > >
> > > will give you all options, in
>> The idea is that you do a
>>
>> fppkg
>>
>> this will look in a database for the package, extract it,
>> and the compile fpmake.pp and run it. The fpmake contains
>> all configuration to make and zip the package.
>>
> Aha, this clears up some mist in my mind. But I still don't really
> understa
On Fri, 10 Aug 2007, Graeme Geldenhuys wrote:
> On 10/08/07, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> >
> > It's super configurable.
> >
> > ./fpmake --help
> >
> > will give you all options, in good unix tradition :-)
>
> And here I thought I would trip you up with my fpGUI example. :)
On 10/08/07, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
>
> It's super configurable.
>
> ./fpmake --help
>
> will give you all options, in good unix tradition :-)
And here I thought I would trip you up with my fpGUI example. :)
Excellent work and thanks for the clear example code.
Regards,
On Fri, 10 Aug 2007, Graeme Geldenhuys wrote:
> On 10/08/07, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
>
> > T:=Targets.AddUnit('myunit');
> > T.ResourceStrings:=True;
> > T:=Targets.AddUnit('myprogram');
> > T.AddDependency('myunit');
>
> Does this take directories as wel
On Fri, 10 Aug 2007, Darius Blaszijk wrote:
> Hi Michael,
>
> Michael Van Canneyt wrote:
> > The idea is that you do a
> >
> > fppkg
> >
> > this will look in a database for the package, extract it, and the compile
> > fpmake.pp and run it. The fpmake contains
> > all configuration to make an
On 10/08/07, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
> T:=Targets.AddUnit('myunit');
> T.ResourceStrings:=True;
> T:=Targets.AddUnit('myprogram');
> T.AddDependency('myunit');
Does this take directories as well?
Here is a fpGUI layout example:
Windows:
src/corelib/gdi/g
Hi Michael,
Michael Van Canneyt wrote:
The idea is that you do a
fppkg
this will look in a database for the package, extract it,
and the compile fpmake.pp and run it. The fpmake contains
all configuration to make and zip the package.
Aha, this clears up some mist in my mind. But I still
Thanks for the quick response Michael. I'll have a look at those files shortly.
Graeme.
On 10/08/07, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
>
> The upcoming 2.2 will contain the basics for a package system.
> Look at all directories in the fpc source dirs. You'll find there
> a fpmake.
On Fri, 10 Aug 2007, Graeme Geldenhuys wrote:
> Hi,
>
> I heard somewhere in a list that Makefile's are on the way out (for
> FPC) and a alternative is in the pipeline. Can anybody shed some
> light on this and if the alternative is usable yet?
>
> I want FPC developers without Lazarus to be
Hi,
I heard somewhere in a list that Makefile's are on the way out (for
FPC) and a alternative is in the pipeline. Can anybody shed some
light on this and if the alternative is usable yet?
I want FPC developers without Lazarus to be able to compile fpGUI.
Before, I tried to use Makefiles, but my
13 matches
Mail list logo
