(Cliff Baeseman) el d�a Mon, 10 May 1999 12:25:32 -0500, escribi�: what about doing…
That would be very very handy I will include the doc in the RPM install....
Cliff

Mailing lists / lazarus / 1999-05
13 messages · 5 people ·
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
(Cliff Baeseman) el d�a Mon, 10 May 1999 12:25:32 -0500, escribi�: what about doing…
That would be very very handy I will include the doc in the RPM install....
Cliff
(Cliff Baeseman) el d�a Mon, 10 May 1999 12:25:32 -0500, escribi�: what about doing…
The gtk 1.2 interface is now also working with the win32 port of GTK.
There need to be done some testing, becuase i don't know if all the bitfield things are correctly aligned, and if the record sizes are correct.
Peter
Oh do not worry we are going to test the hell out of it....
Cliff
Well, I am trying to rebuild the compiler but am getting an error in Linux.pp
(2858,9) Fatal : Syntax error ; expected but identifier K foundNot sure why...
I downloaded all the daliy snapshots and unziped them into correct directorys.
Shane
>> Cliff Baeseman 05/10 12:26 PM >>>
Thanx,
Looks like I will be doing alot of system reconfiguring tonight....
Once I get upgraded I will move lazarus to the 1.2 codebase.
After I complete this I am going to build a RPM that will install lazarus, fcl, compiler and the GTK. I will check everything for required files etc.
If I do this am I going to have to install to a different directory than FPC?
Should I keep our stuff separated, I think that I probably should to avoid conflicts. I can then control
what we are using to avoid compatibility problems. Lazarus will ultimately pass all the switches and paths to the compiler vs using the config unit because those settings are in the project file.
We probably should coordinate this with the FPC fellas. If I do this correctly it will allow easy setup
for someone who does not care to use lazarus but just want's the compiler.
Hopefully this will end most of the New User Problems once and for all....
Cliff
_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus
(Cliff Baeseman) el d�a Mon, 10 May 1999 12:25:32 -0500, escribi�: what about doing…
Cliff Baeseman wroteThat would be very very handy I will include the doc in the RPM install....
ok, I will try to write something for tomorow...
but the /opt directory is not for rpms :)
Sergio
I abourted my attemp to compile the binary. I am having a path problem on my system that…
you wroteOK I will give it a shot when I get home...
Just get:
base.zip
compiler.zip
rtl.zip
unzip all in one directory
copy from base/ the makefile.fpc and makefile to the current directory
type: 'make compiler_all'
and then 'make compiler_install'
I abourted my attemp to compile the binary. I am having a path problem on my system that…
OK I will give it a shot when I get home...
Cliff
Well, I am trying to rebuild the compiler but am getting an error in Linux.pp (2858,9)…
You will have to fix it nico mentioned the error there is a missing semi colon on that line in the source of linux.pp ;)
Cliff
FPC has already his directory in /usr/lib/fpc/$VERSION/ Peter
> btw, I can make a document, if you want, that explains how to setup > all in /opt/fpc and stay to date with the cvs. FPC has already his directory in /usr/lib/fpc/$VERSION/
yep, but I've found more difficult to follow this, I think this is good for packagers, but for people that only work with tar.gz is more easy to use the /opt directory, no need to deal with differents locations, etc. and if you get tired just nuke /opt/fpc :)
I'm thinking in only developers, I expect users to use rpms or debs.
The /opt directory (as defined by the Filesystem Hierarchy Standard -FHS) is where all things not installed by a package, self maintained, should go...
I'm missing something ?
Well, I am trying to rebuild the compiler but am getting an error in Linux.pp (2858,9)…
you wroteWell, I am trying to rebuild the compiler but am getting an error in Linux.pp (2858,9) Fatal : Syntax error ; expected but identifier K found
I added that bug to test how smart you are with fixing bugs ;)
Not sure why... I downloaded all the daliy snapshots and unziped them into correct directorys.
Don't you have CVS ? Then you can use the CVS to update it. See for an explanation what you need and how to install my message from 9 may to fpc-pascal.
(Cliff Baeseman) el d�a Mon, 10 May 1999 12:25:32 -0500, escribi�: what about doing…
FPC has already his directory in /usr/lib/fpc/$VERSION/
Peter
(Cliff Baeseman) el d�a Mon, 10 May 1999
12:25:32 -0500, escribi�:
what about doing no one, but two or three rpms (lazarus, FPC, etc) ?
btw, I can make a document, if you want, that explains how to setup all in /opt/fpc and stay to date with the cvs.
Sergio
I abourted my attemp to compile the binary. I am having a path problem on my system that involves me moving stuff back and forth. First it said it couldn't find systemh.inc so I solved that, now it said ...hmmm...some other file. I'm going to work on the code and Cliff or someone else can create the binary.
My talents (limited) are better served working on the code instead of messing with Linux which I don't fuilly understand yet.
When the binary is updated, let me know.
Shane
>> Peter Vreman 05/10 2:44 PM >>>
I think we should create different RPM's which all depend on eachother
fpc-compiler
fpc-rtl
fpc-fcl
fpc-gtk
and then you can depend lazarus on the needed rpm's. When everything works fine we can even create .rpm snapshots.
And .deb's ofcourse ;)
Except if they still choose to download the .tar.gz instead of the .rpm :)
_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus