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
> Hi,
>
> Can anybody please explain to me FPC packages? I don't understand
> them. I read as much as I could from the docs, but still not sure.
>
> What I understand from packages, is a set of units that work together.
> They don't need to be part of the FPC distribution though.
Correct
>
> S
Hello,
On 8/28/06, Rob van der Linde <[EMAIL PROTECTED]> wrote:
Thank you very much, I was waiting for the release of 2.0.4 so I could
compile .DEB packages for Ubuntu Dapper as I had previously compiled the
2.0.2 release for Ubuntu for people to download. I just found out that
there are now off
Am Dienstag, den 29.08.2006, 23:04 +0200 schrieb Florian Klaempfl:
> Marc Santhoff wrote:
> > Hi,
> >
> > the subject tells most of what i want to know:
> >
> > Which exact models of ARM-cores are supported?
> >
> > Since there are several different ones even in the ARM9 area and I'm
> > thinkin
Can't answer that one for you (perhaps just try?). But I would suggest you
try using prerules to set a variable. The LCLPLATFORM is such a variable in
the lazarus makefiles;
[prerules]
#
# LCL Platform
ifndef LCL_PLATFORM
ifneq ($(findstring $(OS_TARGET),win32 win64),)
LCL_PLATFORM=win32
else
L
On 29 Aug 06, at 21:47, [EMAIL PROTECTED] wrote:
> the filename on the download page is incorrect.
> Should be os2204-full.zip but the hyphen is missing.
Yes. :-( Thanks for the feedback, it should be
fixed now (temporarily - the proper name should
be still without the hyphen, but I have to wai
Marc Santhoff wrote:
> Hi,
>
> the subject tells most of what i want to know:
>
> Which exact models of ARM-cores are supported?
>
> Since there are several different ones even in the ARM9 area and I'm
> thinking about using something like a 920T, 926xx or maybe even PXA255
> I'd like to be sur
the filename on the download page is incorrect.
Should be os2204-full.zip but the hyphen is missing.
I downloaded successfully using ftp.
Thanks.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc
Thanks Tomas, I'll take a look if possible but at present I'm working on
dataabse problems.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
___
fpc-pascal maillist -
Mark Morgan Lloyd wrote:
> Peter Vreman wrote:
>
>> libc is backwards compatible only. That means you can build something
>> with
>> libc-2.2.5 and it will run also on libc-2.3.2. So a fp with debugger
>> build
>> on Woody will also run on Sarge, Etch and Sid.
>
> Thanks Peter, noted. However I'm t
Jonas Maebe wrote:
> On 29 aug 2006, at 14:56, S.Anől Yőlmaz wrote:
>
>> I solved the problem, sort of. :-) In your previous post, you had
>> suggested that I might be using FPIDE, and codepage clash between
>> it and Windows would lead to
>> such a problem. I was using Scite as my IDE in both Wind
On 29 aug 2006, at 14:56, S.Anıl Yılmaz wrote:
I solved the problem, sort of. :-) In your previous post, you had
suggested that I might be using FPIDE, and codepage clash between
it and Windows would lead to
such a problem. I was using Scite as my IDE in both Windows and
Linux, and it had
Hi,
Can anybody please explain to me FPC packages? I don't understand
them. I read as much as I could from the docs, but still not sure.
What I understand from packages, is a set of units that work together.
They don't need to be part of the FPC distribution though.
So could I create my own p
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
Alexey Pavluchenko wrote:
> Hello Tomas,
>
> Monday, August 28, 2006, 10:03:01 PM, you wrote:
>
> TH> I'm happy to announce that release 2.0.4 is
> TH> finally out
>
> Is it just me, or dos204full.zip really can not be downloaded from any
> of the mirrors? If so, why?
Wrong filename. :-( Use dos20
Rimgaudas said,
2) use unicode (UTF-8) enabled editor instead of FP.
Any windows editor will fit too.
I solved the problem, sort of. :-) In your previous post, you had
suggested that I might be using FPIDE, and codepage clash between it and
Windows would lead to
such a problem. I was using Sc
Peter Vreman wrote:
> libc is backwards compatible only. That means you can build something with
> libc-2.2.5 and it will run also on libc-2.3.2. So a fp with debugger build
> on Woody will also run on Sarge, Etch and Sid.
Thanks Peter, noted. However I'm trying to move to faster hardware, not
sl
Florian Klaempfl wrote:
> > I'm still working on other things but that leaves me wondering whether
> > there's scope for the main part of fp and the gdb interface to attempt to
> > use incompatible library versions at runtime. On the machine (Debian
> > "Sarge") I'm using for the build /lib/libc.s
>> I'm still working on other things but that leaves me wondering whether
>> there's
>> scope for the main part of fp and the gdb interface to attempt to use
>> incompatible library versions at runtime. On the machine (Debian
>> "Sarge") I'm
>> using for the build /lib/libc.so.6 -> libc-2.3.2.so, o
Mark Morgan Lloyd wrote:
Tomas Hajny wrote:
I find I can't transfer the compiled bundle to another machine- I get "fp:
/lib/libc.so.6: version `GLIBC_2.3' not found (required by fp)" which I
presume is telling me that it can't find the library version it was built
against. I'm going to drop tha
Tomas Hajny wrote:
> > I find I can't transfer the compiled bundle to another machine- I get "fp:
> > /lib/libc.so.6: version `GLIBC_2.3' not found (required by fp)" which I
> > presume is telling me that it can't find the library version it was built
> > against. I'm going to drop that as an expe
> Hello,
>
> in fpc you have to tell the compiler which registers are used in asm code.
>
> for example
>
> asm
>mov ax,123
> end [eax];
>
> Is it possible to make a compilerswitch that the compiler tells that there
> is
> every register used in asm code? In this case it woult be possible
Hello,
in fpc you have to tell the compiler which registers are used in asm code.
for example
asm
mov ax,123
end [eax];
Is it possible to make a compilerswitch that the compiler tells that there is
every register used in asm code? In this case it woult be possible to port
asm code fro
24 matches
Mail list logo
