Hi,
I committed the new makefiles.
Make in the lazarus dir should make all units and lazarus. Optional targets are lcl and components.
I allso fixed the clean part so a make clean removes all compiled units.
Marc

Mailing lists / lazarus / 2000-04
21 messages · 6 people ·
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Hi,
I committed the new makefiles.
Make in the lazarus dir should make all units and lazarus. Optional targets are lcl and components.
I allso fixed the clean part so a make clean removes all compiled units.
Marc
Marc Weustink wroteHi, I committed the new makefiles.
thanks Marc, Im still having a problem-- now i get: make -C interfaces all
make: Entering an unknown directory
make: *** No such file or directory. Stop.
+ From: Alan Ferguson
+
+ Marc Weustink wrote:
+
+ > Hi,
+ > I committed the new makefiles.
+
+ thanks Marc, Im still having a problem-- now i get:
+ make -C interfaces all
+ make: Entering an unknown directory
+ make: *** No such file or directory. Stop.
Do you have a lazarus/lcl/interfaces dir ??
Marc
Because make will do a 'make all' in $(fpcdir)/rtl/linux and refer to this directory with…
+ From: ]On
+
+ On Mon, 10 Apr 2000, Marc Weustink wrote:
+
+ > The "can't find syslinux" probably comes from an outdated
+ RTL, however I
+ > can't see why adding fpcdir=.. fixed it.
+
+ Because make will do a 'make all' in $(fpcdir)/rtl/linux
???? why would it do a make all in the $(fpcdir)/rtl/linux
+ and refer to this directory with -Fu
the rtl/linux dir is also referenced without it.
Marc
From: Marc Weustink yes, at least this time, I am not sure before. ppc386…
----- Original Message -----
From: Marc Weustink yes, at least this time, I am not sure before. ppc386…
>BTW I did add fpcdir=../[../] as the first makefile change I tried, >but this did not work. I have not tried the above to the Makefile.fpc >as I am unsure of what shell variable it should be assigned to to >make it work.
add the following line in the dirs section of Makfile.fpc : fpcdir=..
save the Makefile.fpc and run fpcmake in this directory. A new makefile is generated.
fpcmake is part of the tools with fpc. It can be checked out with cvs -z3 checkout utils
A make in the utils directory compiles the utility.
Vincent Snijders.
+ From: Vincent Snijders + + I got errors like "can't find syslinux". I got rid of those…
Because make will do a 'make all' in $(fpcdir)/rtl/linux and refer to this directory with -Fu
Michael.
+ From: Vincent Snijders + + I got errors like "can't find syslinux". I got rid of those…
From: Marc Weustink
yes, at least this time, I am not sure before.
BTW, what's the fist line make reports. (the one with a call to ppc386)
ppc386 -Fu/usr/lib/fpc/0.99.15/units/linux -FU../units -di386 gtkwinapiwindow.pp
I have no units in the usr/lib/fpc/0.99.15/units/linux directory.
I committed the new makefiles. Make in the lazarus dir should make all units and lazarus.…
Hi, I committed the new makefiles. Make in the lazarus dir should make all units and lazarus. Optional
targets
are lcl and components.
I got errors like "can't find syslinux". I got rid of those errors by adding fpcdir=..
in the dirs section of lazarus/Makefile.fpc and generating a new makefile. I did the same for the other makefiles.
Is this an appropiate way to solve the missing unit errors?
Regards,
Vincent Snijders
If he has a standard disk setup he can also cd into lazarus/tools and do a python lzbuild.py it has those paths set it in also.
News Release?
Cliff Baeseman
----------------------------------------------------------------- There is nothing wrong with Windows 2000 that LINUX won't fix!!! -----------------------------------------------------------------
+ From: Alan Ferguson + + + > I committed the new makefiles. + + thanks Marc, Im still…
cvs -z3 update -dP lazarus wiil do the trick.
-dP checks out new subdirectories in the current module.
From: Marc Weustink yes, at least this time, I am not sure before. ppc386…
+ From: Vincent Snijders
+
+ > BTW, what's the fist line make reports. (the one with a
+ > call to ppc386)
+ ppc386 -Fu/usr/lib/fpc/0.99.15/units/linux -FU../units -di386
+ gtkwinapiwindow.pp
??? I thought I got more, I'll look at it when I'm at home, can't do it here
+ I have no units in the usr/lib/fpc/0.99.15/units/linux directory.
I didn't use them either. I expected something like ppc386 -Fu/usr/src/fpc/rtl/linux -FU../units -di386 gtkwinapiwindow.pp
or whereever you have your sources.
Marc
From: Marc Weustink yes, at least this time, I am not sure before. ppc386…
I got it, from the early beginnings I still had a FPCDIR environment variable.
This brings me to the following:
Are we going to assume that the fpc dir is always
the parent of the lazarus dir ? So that we define
fpcdir= in the makefiles
or
Are we stating that one should set the FPCDIR
environment variable.
For something foolproof I feel for the first one, for something more flexible I feel for the second on.
Any toughts
Marc
targets I got errors like "can't find syslinux". I got rid of those errors by adding…
+ From: Vincent Snijders
+
+ I got errors like "can't find syslinux". I got rid of those
+ errors by adding
+ fpcdir=..
+ in the dirs section of lazarus/Makefile.fpc and generating a
+ new makefile.
+ I did the same for the other makefiles.
+
+ Is this an appropiate way to solve the missing unit errors?
Nope.
The "can't find syslinux" probably comes from an outdated RTL, however I can't see why adding fpcdir=.. fixed it.
Have you done a make in the rtl dir ??
Marc
BTW, what's the fist line make reports. (the one with a call to ppc386)
From: Marc Weustink yes, at least this time, I am not sure before. ppc386…
Peter Dyson wrotebtw did you get that mwedit92 makefile I sent?
Probably not, when did you send it ?
Marc
+ From: Alan Ferguson + + + > I committed the new makefiles. + + thanks Marc, Im still…
No, and I'm not sure why I don't. Do I have to do more than a cvs update to get this directory?
oops I guess he is running from usr my script will do him no good.
Guess I should recode that tonight to use relative paths and check the installed directories
for common problems.
Cliff Baeseman
---------------------------------------------------------------- There is nothing wrong with Windows 2000 that LINUX won't fix!!! ----------------------------------------------------------------
From: Marc Weustink yes, at least this time, I am not sure before. ppc386…
----- Original Message -----
From: Marc Weustink yes, at least this time, I am not sure before. ppc386…
That's a point
BTW I did add fpcdir=../[../] as the first makefile change I tried, but this did not work. I have not tried the above to the Makefile.fpc as I am unsure of what shell variable it should be assigned to to make it work.
You can always try export FPCDIR="a path to your fpc dir"
Marc
Hi,
I changed the fpcdir in the makefiles so now (hopefully) everthing compiles.
Marc
From: Marc Weustink yes, at least this time, I am not sure before. ppc386…
I favour the first Marc.
I do not run the 'release' version in any way any more as I expect the CVS source tree to be self contained. I could not get the latest files to compile until I did a make install for rtl, fcl, packages. It did this to usr/lib/fpc/0.99.15... which was certainly not what I expect from the makefiles. I thought the point of them was so that development versions are self contained and do not require any of the 'normal' installation configuration files in order to compile the dev versions.
This will probably mean adding the ../fcl/$(OS_SOURCE)..etc to all the makefiles in order to find the latest unit files as found in the dev directory.
BTW I did add fpcdir=../[../] as the first makefile change I tried, but this did not work. I have not tried the above to the Makefile.fpc as I am unsure of what shell variable it should be assigned to to make it work.