Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2010-05

Installing FPC/Lazarus on Windows using SVN, no binaries

55 messages · 16 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Marcos Douglas

Hi,

Whenever I used the Lazarus on Windows, has been through the binary compiled. Simply download and install.
Now I'm want to install Lazarus on Windows but not using the binaries already compiled. The reason is that I want to use SVN to be able to make updates to the sources (FPC and Lazarus) as they are released by the team.

Can I download all the SVN, but if there are problems to compile, I could to use binaries already compiled by the team of Lazarus? Is it the better way?

Now, I'm reading the Wiki Lazarus:
http://wiki.lazarus.freepascal.org/index.php/Getting_Lazarus ...but if someone has a tip, I thanks.

Marcos Douglas

Reply by email

Andrew Brunner
to Marcos Douglas

Check out a local copy of http://svn.freepascal.org/svn/lazarus/trunk in your tortoise svn...

Command prompt ..

make clean all

Marcos Douglas wrote 26 lines
Hi, Whenever I used the Lazarus on Windows, has been through the binary compiled. Simply download and install. Now I'm want to install Lazarus on Windows but not using the binaries already compiled. The reason is that I want to use SVN to be able to make updates to the sources (FPC and Lazarus) as they are released by the team. Can I download all the SVN, but if there are problems to compile, I could to use binaries already compiled by the team of Lazarus? Is it the better way? Now, I'm reading the Wiki Lazarus: http://wiki.lazarus.freepascal.org/index.php/Getting_Lazarus ...but if someone has a tip, I thanks. Marcos Douglas -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Marco van de Voort
to Marcos Douglas: Whenever I used the Lazarus on Windows, has been through the binary compiled. Simply…
Marcos Douglas wrote 10 lines
Whenever I used the Lazarus on Windows, has been through the binary compiled. Simply download and install. Now I'm want to install Lazarus on Windows but not using the binaries already compiled. The reason is that I want to use SVN to be able to make updates to the sources (FPC and Lazarus) as they are released by the team. Can I download all the SVN, but if there are problems to compile, I could to use binaries already compiled by the team of Lazarus? Is it the better way?

In the case of FPC on windows, best to install the last release (2.4.0/win32), take a copy of that dir, and copy the handcompiled snapshot over it.

On *nix you don't need the release so much, and a proper starting compiler is enough to bootstrap afaik everything from SVN.

Reply by email

Marcos Douglas
to Marco van de Voort
Marco van de Voort wrote 7 lines
In the case of FPC on windows, best to install the last release (2.4.0/win32), take a copy of that dir, and copy the handcompiled snapshot over it. On *nix you don't need the release so much, and a proper starting compiler is enough to bootstrap afaik everything from SVN.

I'm downloading Lazarus, from SVN[1], a lot of time... The FPC[2] is with the Lazarus' SVN or I need to pick it apart?

[1] http://svn.freepascal.org/svn/lazarus/trunk
[2] http://svn.freepascal.org/svn/fpc/trunk

Thanks,
Marcos Douglas

Reply by email

Marc Weustink
to Marcos Douglas
Marcos Douglas wrote 13 lines
On Fri, May 28, 2010 at 12:21 PM, Marco van de Voort wrote: > In the case of FPC on windows, best to install the last release > (2.4.0/win32), take a copy of that dir, and copy the handcompiled snapshot > over it. > > On *nix you don't need the release so much, and a proper starting compiler is > enough to bootstrap afaik everything from SVN. I'm downloading Lazarus, from SVN[1], a lot of time... The FPC[2] is with the Lazarus' SVN or I need to pick it apart? [1] http://svn.freepascal.org/svn/lazarus/trunk [2] http://svn.freepascal.org/svn/fpc/trunk

under /svn/lazarus/... there is only lazarus source under /svn/fpc/... there is only fpc source

So you need both.

Marc

Reply by email

Marcos Douglas
to Marc Weustink
Marc Weustink wrote 24 lines
Marcos Douglas wrote: > > On Fri, May 28, 2010 at 12:21 PM, Marco van de Voort > wrote: >> >> In the case of FPC on windows, best to install the last release >> (2.4.0/win32), take a copy of that dir, and copy the handcompiled >> snapshot >> over it. >> >> On *nix you don't need the release so much, and a proper starting >> compiler is >> enough to bootstrap afaik everything from SVN. > > I'm downloading Lazarus, from SVN[1], a lot of time... > The FPC[2] is with the Lazarus' SVN or I need to pick it apart? > > [1] http://svn.freepascal.org/svn/lazarus/trunk > [2] http://svn.freepascal.org/svn/fpc/trunk under /svn/lazarus/... there is only lazarus source under /svn/fpc/... there is only fpc source So you need both.

Hi Marc,
I saw that, but thanks.

Well..
To not have problems to compile FPC and Lazarus on Windows, but continue using SVN for the updates, I received a tip:

- Download a snapshot from ftp://ftp.freepascal.org/pub/lazarus/snapshots/
- Install e.g. c:\lazarus (we would have FPC and Lazarus)
- Get sources at SVN and save e.g. c:\lazarus.svn
- Replace all folders from c:\lazarus.svn to c:\lazarus
- In the Lazarus: Tools -> Configure Build Lazarus -> CleanUp + Build All

This is the best choice for the Windows?
I can do this with FPC too?

Marcos Douglas

Reply by email

Marcos Douglas
to Marcos Douglas
Marcos Douglas wrote 14 lines
Well.. To not have problems to compile FPC and Lazarus on Windows, but continue using SVN for the updates, I received a tip: - Download a snapshot from ftp://ftp.freepascal.org/pub/lazarus/snapshots/ - Install e.g. c:\lazarus (we would have FPC and Lazarus) - Get sources at SVN and save e.g. c:\lazarus.svn - Replace all folders from c:\lazarus.svn to c:\lazarus - In the Lazarus: Tools -> Configure Build Lazarus -> CleanUp + Build All This is the best choice for the Windows? I can do this with FPC too?

Anybody can help me? See above, please.

Marcos Douglas

Reply by email

Felipe Monteiro de Carvalho
to Marcos Douglas: I saw that, but thanks. Well.. To not have problems to compile FPC and Lazarus on…

I usually do like this:

Marcos Douglas wrote
1 - Download a snapshot from ftp://ftp.freepascal.org/pub/lazarus/snapshots/ 2 - Install e.g. c:\lazarus29 (we would have FPC and Lazarus) 3 - Get sources at SVN and save e.g. c:\lazarussvn

4 - Build C:\lazarussvn using the following batch script running from the C:\lazarussvn folder

set path=C:\Programas\lazarus29\fpc\2.4.1\bin\i386-win32 make bigide
pause

5 - Create desktop icons for each startlazarus.exe setting the config path so that they can be used independently

C:\Programas\svnlazarus\startlazarus.exe --primary-config-path=lazarusconf

6 - You can now start your svnlazarus icon, but you need to config some paths in the FPC path

Felipe Monteiro de Carvalho

Reply by email

Marcos Douglas
to Felipe Monteiro de Carvalho

Hi Felipe,
Sorry for late... very busy.

Felipe Monteiro de Carvalho wrote 21 lines
I usually do like this: On Mon, May 31, 2010 at 2:39 PM, Marcos Douglas wrote: > 1 - Download a snapshot from ftp://ftp.freepascal.org/pub/lazarus/snapshots/ > 2 - Install e.g. c:\lazarus29 (we would have FPC and Lazarus) > 3 - Get sources at SVN and save e.g. c:\lazarussvn 4 - Build C:\lazarussvn using the following batch script running from the C:\lazarussvn folder set path=C:\Programas\lazarus29\fpc\2.4.1\bin\i386-win32 make bigide pause 5 - Create desktop icons for each startlazarus.exe setting the config path so that they can be used independently C:\Programas\svnlazarus\startlazarus.exe --primary-config-path=lazarusconf 6 - You can now start your svnlazarus icon, but you need to config some paths in the FPC path

Do not you think better do unlike, how I said (well, my friend said)? Put c:\lazarus_svn in c:\lazarus and Build it.

Marco said like that:

Marco van de Voort wrote 7 lines
In the case of FPC on windows, best to install the last release (2.4.0/win32), take a copy of that dir, and copy the handcompiled snapshot over it. On *nix you don't need the release so much, and a proper starting compiler is enough to bootstrap afaik everything from SVN.

...I think this work better, but I do not know if FPC updates from SVN I can do that too. I can?

Thanks,
Marcos Douglas

Reply by email

Felipe Monteiro de Carvalho
to Marcos Douglas
Marcos Douglas wrote
Do not you think better do unlike, how I said (well, my friend said)? Put c:\lazarus_svn in c:\lazarus and Build it.

Both work the same, do as your prefer.

...I think this work better, but I do not know if FPC updates from SVN I can do that too. I can?

Actually I have forgotten how to build FPC from SVN and integrate it to Lazarus ... It is on my plans to relearn that, maybe in a couple of days ...

The previous instructions were only for Lazarus SVN, not both Lazarus and FPC SVN.

Felipe Monteiro de Carvalho

Reply by email

Marcos Douglas
to Felipe Monteiro de Carvalho
Felipe Monteiro de Carvalho wrote
Both work the same, do as your prefer.

Well, the option "c:\lazarus_svn in c:\lazarus" do not need config anything...

Actually I have forgotten how to build FPC from SVN and integrate it to Lazarus ... It is on my plans to relearn that, maybe in a couple of days ...

Oh, when you know, can you post here or send me? Thanks...

The previous instructions were only for Lazarus SVN, not both Lazarus and FPC SVN.

Ok, I understood.

Marcos Douglas

Reply by email

shoKwave
to Felipe Monteiro de Carvalho: Both work the same, do as your prefer. Actually I have forgotten how to build FPC from…
Felipe Monteiro de Carvalho wrote
Actually I have forgotten how to build FPC from SVN and integrate it to Lazarus ... It is on my plans to relearn that, maybe in a couple of days ...

Hello,
I'm seeking for an "easy" way since some weeks, too. So maybe I can help. ATM the easiest (only?) way I found is:

1. Download an install a precompiled FPC
2. Download FPC-source from SVN (svn co
http://svn.freepascal.org/svn/fpc/trunk fpc)
3. Build FPC (make all)
4. Install FPC (make install INSTALL_PREFIX=x:\path\to\new\fpc )
5. Change/append the PATH environment varible
5.1 Copy all binaries which do not allready exist from old ..\fpc\bin\i386-win32\ to the new one
5.2 Edit fpc.cfg in the new bin and modify the paths
6. Download Lazarus from SVN (svn co
http://svn.freepascal.org/svn/Lazarus/trunk lazarus)
7. Buid Lazarus (make bigide)
8. Open Lazarus and change the paths

Or does someone know an easier/better way? Please tell.

Regards
Ingo

Reply by email

Maxim Ganetsky
to shoKwave

03.06.2010 2:48, shoKwave ?????:

Show quoted text 23 lines
Am 02.06.2010 15:36, schrieb Felipe Monteiro de Carvalho: > Actually I have forgotten how to build FPC from SVN and integrate it > to Lazarus ... It is on my plans to relearn that, maybe in a couple of > days ... Hello, I'm seeking for an "easy" way since some weeks, too. So maybe I can help. ATM the easiest (only?) way I found is: 1. Download an install a precompiled FPC 2. Download FPC-source from SVN (svn co http://svn.freepascal.org/svn/fpc/trunk fpc) 3. Build FPC (make all) 4. Install FPC (make install INSTALL_PREFIX=x:\path\to\new\fpc ) 5. Change/append the PATH environment varible 5.1 Copy all binaries which do not allready exist from old ..\fpc\bin\i386-win32\ to the new one 5.2 Edit fpc.cfg in the new bin and modify the paths 6. Download Lazarus from SVN (svn co http://svn.freepascal.org/svn/Lazarus/trunk lazarus) 7. Buid Lazarus (make bigide) 8. Open Lazarus and change the paths Or does someone know an easier/better way? Please tell.

This is correct and shortest way on Windows AFAICS.

Best regards, Maxim Ganetsky mailto:

Reply by email

Graeme Geldenhuys
to shoKwave: I'm seeking for an "easy" way since some weeks, too. So maybe I can help. ATM the easiest…
shoKwave wrote
Or does someone know an easier/better way? Please tell.

Nope, you hit the nail on the head with that one. That is exactly what I do to (for the last 5 years). And note that step 1 is only every needed once. After that you simply keep using your current compiled binaries and keep recompiling newer and newer SVN versions of FPC and Lazarus.

Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/

Reply by email

Marc Weustink
to Juha Manninen: On Linux I did basically the same thing except for this 5.1. What binaries? This could be…
Juha Manninen wrote 11 lines
> 5.1 Copy all binaries which do not allready exist from old > ..\fpc\bin\i386-win32\ to the new one On Linux I did basically the same thing except for this 5.1. What binaries? > 5.2 Edit fpc.cfg in the new bin and modify the paths This could be documented with more details and placed to wiki for example. There were only 6 lines I had to change but it is not obvious when opening the file for the first time.

:) this is how my ~/.fpc.cfg looks like

#include /etc/fpc.cfg
-Fu/home/marc/lib/fpc/$fpcversion/units/$fpctarget -Fu/home/marc/lib/fpc/$fpcversion/units/$fpctarget/* -Fu/home/marc/lib/fpc/$fpcversion/units/$fpctarget/rtl

This way I can locally install any fpcversion into PREFIX=~

No need to edit

Marc

Reply by email

Juha Manninen
to shoKwave: I'm seeking for an "easy" way since some weeks, too. So maybe I can help. ATM the easiest…
5.1 Copy all binaries which do not allready exist from old ..\fpc\bin\i386-win32\ to the new one

On Linux I did basically the same thing except for this 5.1. What binaries?

5.2 Edit fpc.cfg in the new bin and modify the paths

This could be documented with more details and placed to wiki for example. There were only 6 lines I had to change but it is not obvious when opening the file for the first time.

Now this process is documented somewhere inside a 1000-page (or something) FPC manual. I don't even know where.

Juha

Reply by email

Graeme Geldenhuys
to Marc Weustink: :) this is how my ~/.fpc.cfg looks like #include /etc/fpc.cfg…
Marc Weustink wrote
:) this is how my ~/.fpc.cfg looks like

I have the same as you, but I install FPC to:

/opt/fpc_<version>/<targetcpu>-<targetos>/

...using the INSTALL_PREFIX parameter

eg:

make clean
make all PP=/opt/fpc_2.4.1/x86_64-linux/bin/ppcx64 make install INSTALL_PREFIX=/opt/fpc_2.5.1/x86_64-linux/ PP=/opt/fpc_2.4.1/x86_64-linux/bin/ppcx64

Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/

Reply by email

shoKwave
to Juha Manninen: On Linux I did basically the same thing except for this 5.1. What binaries? This could be…
Juha Manninen wrote 7 lines
> 5.1 Copy all binaries which do not allready exist from old > ..\fpc\bin\i386-win32\ to the new one > On Linux I did basically the same thing except for this 5.1. What binaries?

On Windows FPC comes with several tools like make, cp, rm... which don't exist on Windows nativly. So when you change the PATH this tools aren't in PATH anymore.

Reply by email

Graeme Geldenhuys
to shoKwave
shoKwave wrote
On Windows FPC comes with several tools like make, cp, rm... which don't exist on Windows nativly. So when you change the PATH this tools aren't in PATH anymore.

Simply keep them in a separate directory that also has a PATH entry. I have the following under Windows.

c:\fpc\binutils\
c:\fpc\<version>\

Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/

Reply by email

shoKwave
to Juha Manninen
Juha Manninen wrote 5 lines
Ah, yes. With Linux everything is so much easier :-)

I don't think so. On Linux first you have to check all depending packages (gdk-pixbuf-devel, gtk2-devel, libQt4-devel...) are installed and on some distros packages are named different. Then do all things discriped( without 5.1). And then you have create a symlink to your ppcxxx binary by hand.

All platforms have their pros and cons.

What about MacOS X. As far as I tested yet it should be the same as Linux. Am I right? A ".fpc.cfg" in HOME works, but how can I append the PATH? Is there a ".profile" too?

Reply by email

Juha Manninen
to shoKwave
shoKwave wrote 5 lines
I don't think so. On Linux first you have to check all depending packages (gdk-pixbuf-devel, gtk2-devel, libQt4-devel...) are installed and on some distros packages are named different. Then do all things discriped( without 5.1). And then you have create a symlink to your ppcxxx binary by hand.

The first part is true but I didn't create symlinks by hand. "make install..." made it I guess.

Show quoted text 5 lines
All platforms have their pros and cons. What about MacOS X. As far as I tested yet it should be the same as Linux. Am I right? A ".fpc.cfg" in HOME works, but how can I append the PATH? Is there a ".profile" too?

Beneath the surface Mac is a full UNIX system.
Command line and config files should be pretty much like in Linux. Unfortunately I don't have a Mac so I am not sure of the details.

Juha

Reply by email

Marcos Douglas
to Graeme Geldenhuys: Simply keep them in a separate directory that also has a PATH entry. I have the following…
Graeme Geldenhuys wrote 11 lines
On 3 June 2010 12:16, shoKwave wrote: > > On Windows FPC comes with several tools like make, cp, rm... which don't > exist on Windows nativly. So when you change the PATH this tools aren't in > PATH anymore. Simply keep them in a separate directory that also has a PATH entry. I have the following under Windows. c:\fpc\binutils\ c:\fpc\<version>\

One more tip... this should be more explicit in the installation on Windows. It seems that each person makes his way :( I used the Felipe Monteiro de Carvalho method. But his method is more for Lazarus, not FPC, I think.

I will try Ingo(shoKwave) method too.

Thanks,
Marcos Douglas

Reply by email

shoKwave
to Marcos Douglas
Marcos Douglas wrote 11 lines
Simply keep them in a separate directory that also has a PATH entry. I > have the following under Windows. > > c:\fpc\binutils\ > c:\fpc\<version>\ > One more tip... this should be more explicit in the installation on Windows. It seems that each person makes his way :( I used the Felipe Monteiro de Carvalho method. But his method is more for Lazarus, not FPC, I think.

Felipe explained the way to install multiple installations of Lazarus. Greames hint discribes a more elegant way of handling additional tools which are not part of the FPC-Project but needed to build FPC and Lazarus.

I discriped the way how I install the SVN-Versions of FPC and Lazarus on a clean System.

So you can/have to choose what you need to reach your goal. :-)

regards,
Ingo

Reply by email

shoKwave
to Juha Manninen: The first part is true but I didn't create symlinks by hand. "make install..." made it I…
Juha Manninen wrote 11 lines
shoKwave wrote: > I don't think so. On Linux first you have to check all depending > packages (gdk-pixbuf-devel, gtk2-devel, libQt4-devel...) are installed > and on some distros packages are named different. Then do all things > discriped( without 5.1). And then you have create a symlink to your > ppcxxx binary by hand. > The first part is true but I didn't create symlinks by hand. "make install..." made it I guess.

I just tested make install to a new diretory but there is no ppc-binary/-link. Maybe we can say:

begin
   if not FileExists('bin/ppci386') then
     CreatePPCLink;
end;

:D

Reply by email

Marcos Douglas
to shoKwave: Felipe explained the way to install multiple installations of Lazarus. Greames hint…
shoKwave wrote 9 lines
Felipe explained the way to install multiple installations of Lazarus. Greames hint discribes a more elegant way of handling additional tools which are not part of the FPC-Project but needed to build FPC and Lazarus. I discriped the way how I install the SVN-Versions of FPC and Lazarus on a clean System. So you can/have to choose what you need to reach your goal. :-)

Some people updates only Lazarus, others FPC and Lazarus... others just install on Windows, without SVN. Because that, each one has a solution :)

I want update FPC and Lazarus using SVN. I will try do that following the instructions... thanks.

Marcos Douglas

Reply by email

Dimitrios Chr. Ioannidis
to shoKwave: I'm seeking for an "easy" way since some weeks, too. So maybe I can help. ATM the easiest…

Hi,

Or does someone know an easier/better way? Please tell.

just my 2 ...

Plz, replace the .. with the full path.

get the last fpc binary only ....

make a dir tree something like

..\FreePascal
..\FreePascal\binutils
..\FreePascal\binutils\arm-wince
..\FreePascal\binutils\i386-win32
..\FreePascal\binutils\x86_64-win64
..\FreePascal\fpc\source
..\FreePascal\fpc\svn
..\FreePascal\lazarus

place the latest stable only ppc386.exe in ..\FreePascal\binutils

for binutils

checkout the
http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_4/install/crossbinwce or http://svn.freepascal.org/svn/fpcbuild/trunk/install/crossbinwce at ..\FreePascal\binutils\arm-wince

similar checkout the
http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_4/install/binw32 or http://svn.freepascal.org/svn/fpcbuild/branches/trunk/install/binw32 at ..\FreePascal\binutils\i386-win32

dido similar checkout the
http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_4/install/binw64 or http://svn.freepascal.org/svn/fpcbuild/branches/trunk/install/binw64 at ..\FreePascal\binutils\x86_64-win64

checkout the http://svn.freepascal.org/svn/fpc/branches/fixes_2_4 or http://svn.freepascal.org/svn/fpc/trunk in ..\FreePascal\fpc\svn

checkout the http://svn.freepascal.org/svn/lazarus/trunk in ..\FreePascal\lazarus

now every time you want a new fpc and lazarus recompiled make a bat file similar to this and run it.

---

@echo off

TortoiseProc.exe /command:update
/path:"..\FreePascal\binutils\arm-wince" /closeonend:3 TortoiseProc.exe /command:update
/path:"..\FreePascal\binutils\i386-win32" /closeonend:3 TortoiseProc.exe /command:update
/path:"..\FreePascal\binutils\x86_64-win64" /closeonend:3 TortoiseProc.exe /command:update /path:"..\FreePascal\fpc\svn" /closeonend:3 TortoiseProc.exe /command:export /path:"..\FreePascal\fpc\svn" /closeonend:3 rmdir /S /Q "..\FreePascal\fpc\bin"
rmdir /S /Q "..\FreePascal\fpc\doc"
rmdir /S /Q "..\FreePascal\fpc\examples"
rmdir /S /Q "..\FreePascal\fpc\msg"
rmdir /S /Q "..\FreePascal\fpc\units"
move "..\FreePascal\fpc\source\svn" "..\FreePascal\fpc\source" /Y TortoiseProc.exe /command:update /path:"..\FreePascal\lazarus" /closeonend:3

set
path=..\FreePascal\binutils\i386-win32;..\FreePascal\binutils\x86_64-win64;..\FreePascal\binutils\arm-wince;..\FreePascal\fpc\source\utils\fpcm;%path%

cd ..\FreePascal\fpc\source

make distclean OS_TARGET=win32 CPU_TARGET=i386
FPC=..\FreePascal\binutils\ppc386.exe
make distclean OS_TARGET=win64 CPU_TARGET=x86_64
FPC=..\FreePascal\binutils\ppc386.exe
make distclean OS_TARGET=wince CPU_TARGET=arm
FPC=..\FreePascal\binutils\ppc386.exe

make all install OS_TARGET=win32 CPU_TARGET=i386 UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=..\FreePascal\fpc
FPC=..\FreePascal\binutils\ppc386.exe

copy ..\FreePascal\binutils\fpc.cfg ..\FreePascal\fpc\bin\i386-win32

set path=..\FreePascal\fpc\bin\i386-win32;%path%

make all crossinstall OS_TARGET=win64 CPU_TARGET=x86_64 UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=..\FreePascal\fpc

make all crossinstall OS_TARGET=wince CPU_TARGET=arm UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=..\FreePascal\fpc BINUTILSPREFIX=arm-wince-

cd ..\FreePascal\lazarus

make distclean

make all OPT="-glw2"

pause

---

regards,

Dimitrios Chr. Ioannidis

Reply by email

waldo kitty
to Dimitrios Chr. Ioannidis
Dimitrios Chr. Ioannidis wrote 8 lines
Hi, > Or does someone know an easier/better way? Please tell. just my 2 ... Plz, replace the .. with the full path.

[trim excellent instructions]

now that looks like a viable answer to my recent question about easily adding multiple cross-platform capabilities to an existing Lazarus install... granted, it uses svn instead of archives as i had suggested for a possibility but it looks quite workable...

i think i like it! :)

Reply by email

Graeme Geldenhuys
to Dimitrios Chr. Ioannidis: just my 2 ... Plz, replace the .. with the full path. get the last fpc binary only ....…
Dimitrios Chr. Ioannidis wrote
..\FreePascal\fpc\source ..\FreePascal\fpc\svn

Your setup is very similar to my linux setup. But what is the difference between the 'svn' and 'source' directories listed above? In my case I only have 'src' which is the checked out code from SubVersion.

Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/

Reply by email

Marcos Douglas
to Dimitrios Chr. Ioannidis: just my 2 ... Plz, replace the .. with the full path. get the last fpc binary only ....…
Dimitrios Chr. Ioannidis wrote 109 lines
Hi, > Or does someone know an easier/better way? Please tell. just my 2 ... Plz, replace the .. with the full path. get the last fpc binary only .... make a dir tree something like ..\FreePascal ..\FreePascal\binutils ..\FreePascal\binutils\arm-wince ..\FreePascal\binutils\i386-win32 ..\FreePascal\binutils\x86_64-win64 ..\FreePascal\fpc\source ..\FreePascal\fpc\svn ..\FreePascal\lazarus place the latest stable only ppc386.exe in ..\FreePascal\binutils for binutils checkout the http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_4/install/crossbinwce or http://svn.freepascal.org/svn/fpcbuild/trunk/install/crossbinwce at ..\FreePascal\binutils\arm-wince similar checkout the http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_4/install/binw32 or http://svn.freepascal.org/svn/fpcbuild/branches/trunk/install/binw32 at ..\FreePascal\binutils\i386-win32 dido similar checkout the http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_4/install/binw64 or http://svn.freepascal.org/svn/fpcbuild/branches/trunk/install/binw64 at ..\FreePascal\binutils\x86_64-win64 checkout the http://svn.freepascal.org/svn/fpc/branches/fixes_2_4 or http://svn.freepascal.org/svn/fpc/trunk in ..\FreePascal\fpc\svn checkout the http://svn.freepascal.org/svn/lazarus/trunk in ..\FreePascal\lazarus now every time you want a new fpc and lazarus recompiled make a bat file similar to this and run it. --- @echo off TortoiseProc.exe /command:update /path:"..\FreePascal\binutils\arm-wince" /closeonend:3 TortoiseProc.exe /command:update /path:"..\FreePascal\binutils\i386-win32" /closeonend:3 TortoiseProc.exe /command:update /path:"..\FreePascal\binutils\x86_64-win64" /closeonend:3 TortoiseProc.exe /command:update /path:"..\FreePascal\fpc\svn" /closeonend:3 TortoiseProc.exe /command:export /path:"..\FreePascal\fpc\svn" /closeonend:3 rmdir /S /Q "..\FreePascal\fpc\bin" rmdir /S /Q "..\FreePascal\fpc\doc" rmdir /S /Q "..\FreePascal\fpc\examples" rmdir /S /Q "..\FreePascal\fpc\msg" rmdir /S /Q "..\FreePascal\fpc\units" move "..\FreePascal\fpc\source\svn" "..\FreePascal\fpc\source" /Y TortoiseProc.exe /command:update /path:"..\FreePascal\lazarus" /closeonend:3 set path=..\FreePascal\binutils\i386-win32;..\FreePascal\binutils\x86_64-win64;..\FreePascal\binutils\arm-wince;..\FreePascal\fpc\source\utils\fpcm;%path% cd ..\FreePascal\fpc\source make distclean OS_TARGET=win32 CPU_TARGET=i386 FPC=..\FreePascal\binutils\ppc386.exe make distclean OS_TARGET=win64 CPU_TARGET=x86_64 FPC=..\FreePascal\binutils\ppc386.exe make distclean OS_TARGET=wince CPU_TARGET=arm FPC=..\FreePascal\binutils\ppc386.exe make all install OS_TARGET=win32 CPU_TARGET=i386 UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=..\FreePascal\fpc FPC=..\FreePascal\binutils\ppc386.exe copy ..\FreePascal\binutils\fpc.cfg ..\FreePascal\fpc\bin\i386-win32 set path=..\FreePascal\fpc\bin\i386-win32;%path% make all crossinstall OS_TARGET=win64 CPU_TARGET=x86_64 UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=..\FreePascal\fpc make all crossinstall OS_TARGET=wince CPU_TARGET=arm UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=..\FreePascal\fpc BINUTILSPREFIX=arm-wince- cd ..\FreePascal\lazarus make distclean make all OPT="-glw2" pause

I made my own script (below), but I have some doubts:

#################################################################### @echo on

TortoiseProc.exe /command:update
/path:"c:\freepascal\binutils\arm-wince" /closeonend:3 TortoiseProc.exe /command:update
/path:"c:\freepascal\binutils\i386-win32" /closeonend:3 TortoiseProc.exe /command:update
/path:"c:\freepascal\binutils\x86_64-win64" /closeonend:3 TortoiseProc.exe /command:update /path:"c:\freepascal\fpc" /closeonend:3 TortoiseProc.exe /command:update /path:"c:\freepascal\lazarus" /closeonend:3

set path=c:\freepascal\binutils\i386-win32;c:\freepascal\binutils\x86_64-win64;c:\freepascal\binutils\arm-wince;c:\freepascal\fpc\utils\fpcm;%path%

cd c:\freepascal\fpc

make distclean OS_TARGET=win32 CPU_TARGET=i386
FPC=c:\freepascal\binutils\ppc386.exe
make distclean OS_TARGET=win64 CPU_TARGET=x86_64
FPC=c:\freepascal\binutils\ppc386.exe
make distclean OS_TARGET=wince CPU_TARGET=arm
FPC=c:\freepascal\binutils\ppc386.exe

make all install OS_TARGET=win32 CPU_TARGET=i386 UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=c:\freepascal\fpc
FPC=c:\freepascal\binutils\ppc386.exe

copy c:\freepascal\binutils\fpc.cfg c:\freepascal\fpc\bin\i386-win32

set path=c:\freepascal\fpc\bin\i386-win32;%path%

make all crossinstall OS_TARGET=win64 CPU_TARGET=x86_64 UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=c:\freepascal\fpc
make all crossinstall OS_TARGET=wince CPU_TARGET=arm UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=c:\freepascal\fpc BINUTILSPREFIX=arm-wince-

cd c:\freepascal\lazarus

make distclean

make all OPT="-glw2"

pause
####################################################################

line: copy c:\freepascal\binutils\fpc.cfg c:\freepascal\fpc\bin\i386-win32 Who makes this file? It does exists in SVN.

----------------------------------

lines:
make all crossinstall OS_TARGET=win64 CPU_TARGET=x86_64 UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=c:\freepascal\fpc

make all crossinstall OS_TARGET=wince CPU_TARGET=arm UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=c:\freepascal\fpc BINUTILSPREFIX=arm-wince-

These lines are necessary?

----------------------------------

line: make all OPT="-glw2"

ERROR:

C:\freepascal\lazarus>make all OPT="-glw2"
make -C lcl all
make[1]: Entering directory `C:/freepascal/lazarus/lcl' c:/freepascal/binutils/i386-win32/rm.exe -f units/i386-win32/alllclunits.ppu c:/freepascal/binutils/i386-win32/gmkdir.exe -p units/i386-win32 c:/freepascal/fpc/bin/i386-win32/ppc386.exe -gl -Fu. -Fuforms -Fuwidgetset -Fii nclude -FE. -FUunits/i386-win32 -glw2 -di386 alllclunits.pp Free Pascal Compiler version 2.5.1 [2010/06/04] for i386 Copyright (c) 1993-2009 by Florian Klaempfl
Target OS: Win32 for i386
Compiling alllclunits.pp
Fatal: Can't find unit system used by AllLCLUnits
Fatal: Compilation aborted
make[1]: *** [alllclunits.ppu] Error 1
make[1]: Leaving directory `C:/freepascal/lazarus/lcl' make: *** [lcl] Error 2

----------------------------------

Somebody can help me?

Thanks,
Marcos Douglas

Reply by email

Marcos Douglas
to Marcos Douglas
Marcos Douglas wrote 20 lines
line: make all OPT="-glw2" ERROR: C:\freepascal\lazarus>make all OPT="-glw2" make -C lcl all make[1]: Entering directory `C:/freepascal/lazarus/lcl' c:/freepascal/binutils/i386-win32/rm.exe -f units/i386-win32/alllclunits.ppu c:/freepascal/binutils/i386-win32/gmkdir.exe -p units/i386-win32 c:/freepascal/fpc/bin/i386-win32/ppc386.exe -gl ?-Fu. -Fuforms -Fuwidgetset -Fii nclude -FE. -FUunits/i386-win32 -glw2 -di386 alllclunits.pp Free Pascal Compiler version 2.5.1 [2010/06/04] for i386 Copyright (c) 1993-2009 by Florian Klaempfl Target OS: Win32 for i386 Compiling alllclunits.pp Fatal: Can't find unit system used by AllLCLUnits Fatal: Compilation aborted make[1]: *** [alllclunits.ppu] Error 1 make[1]: Leaving directory `C:/freepascal/lazarus/lcl' make: *** [lcl] Error 2

The directory:
C:\freepascal\lazarus\lcl\units\i386-win32\

...is empty!

Thanks,
Marcos Douglas

Reply by email

Marcos Douglas
to Marcos Douglas
Marcos Douglas wrote 26 lines
On Fri, Jun 4, 2010 at 2:59 PM, Marcos Douglas wrote: > line: make all OPT="-glw2" > > ERROR: > > C:\freepascal\lazarus>make all OPT="-glw2" > make -C lcl all > make[1]: Entering directory `C:/freepascal/lazarus/lcl' > c:/freepascal/binutils/i386-win32/rm.exe -f units/i386-win32/alllclunits.ppu > c:/freepascal/binutils/i386-win32/gmkdir.exe -p units/i386-win32 > c:/freepascal/fpc/bin/i386-win32/ppc386.exe -gl ?-Fu. -Fuforms -Fuwidgetset -Fii > nclude -FE. -FUunits/i386-win32 -glw2 -di386 alllclunits.pp > Free Pascal Compiler version 2.5.1 [2010/06/04] for i386 > Copyright (c) 1993-2009 by Florian Klaempfl > Target OS: Win32 for i386 > Compiling alllclunits.pp > Fatal: Can't find unit system used by AllLCLUnits > Fatal: Compilation aborted > make[1]: *** [alllclunits.ppu] Error 1 > make[1]: Leaving directory `C:/freepascal/lazarus/lcl' > make: *** [lcl] Error 2 The directory: C:\freepascal\lazarus\lcl\units\i386-win32\ ...is empty!

Hi all,

I found the problem: fpc.cfg
Tip: http:/msg20003.html

Before, I had this file created by Installer. I just copy it to c:\freepascal\fpc\bin\i386-win32 because is necessary to the script.

So, the Lazarus was compiled, but yours paths is set to: FPC source directory:
C:\freepascal\lazarus\fpc\2.4.1\source\

Make path:
C:\freepascal\lazarus\fpc\2.4.1\bin\i386-win32\make.exe

...even if I change this, an error happen:
"The Free Pascal compiler (filename: fpc.exe) was not found. It is recommended that you install fpc."

Marcos Douglas

Reply by email

Marcos Douglas
to Marcos Douglas
Marcos Douglas wrote 18 lines
Hi all, I found the problem: fpc.cfg Tip: http:/msg20003.html Before, I had this file created by Installer. I just copy it to c:\freepascal\fpc\bin\i386-win32 because is necessary to the script. So, the Lazarus was compiled, but yours paths is set to: FPC source directory: C:\freepascal\lazarus\fpc\2.4.1\source\ Make path: C:\freepascal\lazarus\fpc\2.4.1\bin\i386-win32\make.exe ...even if I change this, an error happen: "The Free Pascal compiler (filename: fpc.exe) was not found. It is recommended that you install fpc."

Plese, somebody knows the problem?

Thanks,
Marcos Douglas

Reply by email

Mattias Gaertner
to Marcos Douglas
Show quoted text 21 lines
On Fri, Jun 4, 2010 at 4:47 PM, Marcos Douglas wrote: > Hi all, > > I found the problem: fpc.cfg > Tip: http:/msg20003.html > > Before, I had this file created by Installer. I just copy it to > c:\freepascal\fpc\bin\i386-win32 because is necessary to the script. > > So, the Lazarus was compiled, but yours paths is set to: > FPC source directory: > C:\freepascal\lazarus\fpc\2.4.1\source\ > > Make path: > C:\freepascal\lazarus\fpc\2.4.1\bin\i386-win32\make.exe > > ...even if I change this, an error happen: > "The Free Pascal compiler (filename: fpc.exe) was not found. > It is recommended that you install fpc." Plese, somebody knows the problem?

Check Environment Options / compiler path.
If there is 'fpc.exe' then the IDE has not found fpc.exe in the paths of your system PATH variable. You can try a full file name.

Mattias

Reply by email

Marcos Douglas
to Mattias Gaertner

Hi Mattias,

Mattias Gaertner wrote
Check Environment Options / compiler path. If there is 'fpc.exe' then the IDE has not found fpc.exe in the paths of your system PATH variable. You can try a full file name.

There is 'fcp.exe' in the configuration...
What paths I have to put in PATH variable?

When I downloaded the FPC, I put in c:\freepascal\fpc\ without directory for version. I might have problems with this?

Thanks,
Marcos Douglas

Reply by email

Thierry Bothorel
to Marcos Douglas

Marcos Douglas a ?crit :

Show quoted text 21 lines
Hi Mattias, On Sat, Jun 5, 2010 at 1:22 PM, Mattias Gaertner wrote: > Check Environment Options / compiler path. > If there is 'fpc.exe' then the IDE has not found fpc.exe in the > paths of your system PATH variable. You can try a full file name. > There is 'fcp.exe' in the configuration... What paths I have to put in PATH variable? When I downloaded the FPC, I put in c:\freepascal\fpc\ without directory for version. I might have problems with this? Thanks, Marcos Douglas

Hi,

I use three Lazarus versions on Windows with three FPC versions. If you always use Lazarus to code freepascal, then you do not need to add FPC to your PATH, Lazarus handle this with its options. But FPC stand-alone setup adds itself to system PATH, and it cause trouble with Lazarus as I experience, so I just removes it from PATH.

Thierry

Reply by email

Mattias Gaertner
to Marcos Douglas: On Sat, Jun 5, 2010 at 1:22 PM, Mattias Gaertner There is 'fcp.exe' in the…
Show quoted text 14 lines
Hi Mattias, On Sat, Jun 5, 2010 at 1:22 PM, Mattias Gaertner wrote: > > Check Environment Options / compiler path. > If there is 'fpc.exe' then the IDE has not found fpc.exe in the > paths of your system PATH variable. You can try a full file name. There is 'fcp.exe' in the configuration... What paths I have to put in PATH variable? When I downloaded the FPC, I put in c:\freepascal\fpc\ without directory for version. I might have problems with this?

You can put fpc anywhere you want as long as you don't use spaces in the paths. Just put the full file name in the environment option OR add the directory where fpc.exe is to your PATH variable. The later can be useful when compiling via console.

Mattias

Reply by email

Hans-Peter Diettrich
to Marcos Douglas: Plese, somebody knows the problem? Marcos Douglas
> Before, I had this file created by Installer. I just copy it to > c:\freepascal\fpc\bin\i386-win32 because is necessary to the script.

The bin directory should be in the path, so that all scripts can find the programs. I made an build.bat file that sets the path accordingly, and then invokes make. When executed from a console, the path is set for issuing further commands.

@echo Installing Lazarus
path=C:\FPC\2.4.0\bin\i386-win32;D:\SourceForge\Lazarus cd ide
windres -i lazarus.rc -o lazarus.res
cd ..
make
rem make clean all (if required), then make bigide @echo Did you already create a desktop icon to the new Lazarus.exe?

DoDi

Reply by email

Marcos Douglas
to Hans-Peter Diettrich
Thierry Bothorel wrote 6 lines
I use three Lazarus versions on Windows with three FPC versions. If you always use Lazarus to code freepascal, then you do not need to add FPC to your PATH, Lazarus handle this with its options. But FPC stand-alone setup adds itself to system PATH, and it cause trouble with Lazarus as I experience, so I just removes it from PATH.
Mattias Gaertner wrote 5 lines
You can put fpc anywhere you want as long as you don't use spaces in the paths. Just put the full file name in the environment option OR add the directory where fpc.exe is to your PATH variable. The later can be useful when compiling via console.
Hans-Peter Diettrich wrote 14 lines
The bin directory should be in the path, so that all scripts can find the programs. I made an build.bat file that sets the path accordingly, and then invokes make. When executed from a console, the path is set for issuing further commands. @echo Installing Lazarus path=C:\FPC\2.4.0\bin\i386-win32;D:\SourceForge\Lazarus cd ide windres -i lazarus.rc -o lazarus.res cd .. make rem make clean all (if required), then make bigide @echo Did you already create a desktop icon to the new Lazarus.exe?

Thanks guys.
I added fpc.exe in PATH and it worked. No more erros when start Lazarus...

...but I found another error now :(

I just reverse the FPC version 2.5.1 (trunk) to 2.4.1 (fixes_2_4) because I want to work in the stable compiler.
So, I switch /fpc/trunk to /fpc/branches/fixes_2_4/ and compiled without errors.

When I tried to compile Lazarus (/trunk) got the following errors:

C:\freepascal\lazarus>make all OPT="-glw2"
make -C lcl all
make[1]: Entering directory `C:/freepascal/lazarus/lcl' c:/freepascal/binutils/i386-win32/rm.exe -f units/i386-win32/alllclunits.ppu c:/freepascal/binutils/i386-win32/gmkdir.exe -p units/i386-win32 c:/freepascal/fpc/bin/i386-win32/ppc386.exe -gl -Fu. -Fuforms -Fuwidgetset -Fi nclude -FE. -FUunits/i386-win32 -glw2 -di386 alllclunits.pp Free Pascal Compiler version 2.4.1 [2010/06/07] for i386 Copyright (c) 1993-2009 by Florian Klaempfl
Target OS: Win32 for i386
Compiling alllclunits.pp
Compiling lclversion.pas
Compiling lclstrconsts.pas
Writing Resource String Table file: lclstrconsts.rst Compiling fpcadds.pas
Compiling lazlinkedlist.pas
Compiling dynhasharray.pp
Compiling lclproc.pas
Compiling avglvltree.pas
Compiling fileutil.pas
Compiling masks.pas
PPU Loading C:\freepascal\fpc\units\i386-win32\fcl-base\contnrs.ppu PPU Invalid Version 119
Fatal: Can't find unit Contnrs used by Masks
Fatal: Compilation aborted
make[1]: *** [alllclunits.ppu] Error 1
make[1]: Leaving directory `C:/freepascal/lazarus/lcl' make: *** [lcl] Error 2

The BAT file is attached.
What version of FPC the Lazarus works well?

Marcos Douglas
-------------- next part --------------
@echo on

set path=c:\freepascal\binutils\i386-win32;c:\freepascal\binutils\x86_64-win64;c:\freepascal\binutils\arm-wince;c:\freepascal\fpc\utils\fpcm;%path%

cd c:\freepascal\fpc

make distclean OS_TARGET=win32 CPU_TARGET=i386 FPC=c:\freepascal\binutils\ppc386.exe make distclean OS_TARGET=win64 CPU_TARGET=x86_64 FPC=c:\freepascal\binutils\ppc386.exe make distclean OS_TARGET=wince CPU_TARGET=arm FPC=c:\freepascal\binutils\ppc386.exe

make all install OS_TARGET=win32 CPU_TARGET=i386 UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=c:\freepascal\fpc FPC=c:\freepascal\binutils\ppc386.exe

copy c:\freepascal\binutils\fpc.cfg c:\freepascal\fpc\bin\i386-win32 /Y

set path=c:\freepascal\fpc\bin\i386-win32;%path%

make all crossinstall OS_TARGET=win64 CPU_TARGET=x86_64 UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=c:\freepascal\fpc make all crossinstall OS_TARGET=wince CPU_TARGET=arm UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=c:\freepascal\fpc BINUTILSPREFIX=arm-wince-

cd c:\freepascal\lazarus

make distclean
make all OPT="-glw2"

pause

Reply by email

Mattias Gärtner
to Marcos Douglas

Zitat von Marcos Douglas :

Show quoted text 5 lines
[...] Free Pascal Compiler version 2.4.1 [2010/06/07] for i386 [...] PPU Loading C:\freepascal\fpc\units\i386-win32\fcl-base\contnrs.ppu PPU Invalid Version 119

It means, you have a ppu compiled with another compiler.

[...] What version of FPC the Lazarus works well?

Both 2.4.1 and 2.5.1 work well.
But you have to make sure that the FPC installation is not mixed. That means before you install FPC into a directory, delete the units directory.

Mattias

Reply by email

Marcos Douglas
to Mattias Gärtner

2010/6/7 Mattias G?rtner :

Show quoted text 16 lines
Zitat von Marcos Douglas : > [...] > Free Pascal Compiler version 2.4.1 [2010/06/07] for i386 > [...] > PPU Loading C:\freepascal\fpc\units\i386-win32\fcl-base\contnrs.ppu > PPU Invalid Version 119 It means, you have a ppu compiled with another compiler. > [...] > What version of FPC the Lazarus works well? Both 2.4.1 and 2.5.1 work well. But you have to make sure that the FPC installation is not mixed. That means before you install FPC into a directory, delete the units directory.

First I compiled FPC 2.5.1. But now, I change to 2.4.1 and compiled. The command "Switch", in SVN, not do that?

Marcos Douglas

Reply by email

Mattias Gärtner
to Marcos Douglas

Zitat von Marcos Douglas :

Show quoted text 20 lines
2010/6/7 Mattias G?rtner : > Zitat von Marcos Douglas : > >> [...] >> Free Pascal Compiler version 2.4.1 [2010/06/07] for i386 >> [...] >> PPU Loading C:\freepascal\fpc\units\i386-win32\fcl-base\contnrs.ppu >> PPU Invalid Version 119 > > It means, you have a ppu compiled with another compiler. > >> [...] >> What version of FPC the Lazarus works well? > > Both 2.4.1 and 2.5.1 work well. > But you have to make sure that the FPC installation is not mixed. That means > before you install FPC into a directory, delete the units directory. First I compiled FPC 2.5.1. But now, I change to 2.4.1 and compiled. The command "Switch", in SVN, not do that?

The svn switch handles only the source files.
The ppu files are created by you when you do 'make install'. And 'make install' does not uninstall any old ppu files.

Mattias

Reply by email

Marcos Douglas
to Mattias Gärtner

2010/6/7 Mattias G?rtner :

Show quoted text 29 lines
Zitat von Marcos Douglas : > 2010/6/7 Mattias G?rtner : >> >> Zitat von Marcos Douglas : >> >>> [...] >>> Free Pascal Compiler version 2.4.1 [2010/06/07] for i386 >>> [...] >>> PPU Loading C:\freepascal\fpc\units\i386-win32\fcl-base\contnrs.ppu >>> PPU Invalid Version 119 >> >> It means, you have a ppu compiled with another compiler. >> >>> [...] >>> What version of FPC the Lazarus works well? >> >> Both 2.4.1 and 2.5.1 work well. >> But you have to make sure that the FPC installation is not mixed. That >> means >> before you install FPC into a directory, delete the units directory. > > First I compiled FPC 2.5.1. But now, I change to 2.4.1 and compiled. > The command "Switch", in SVN, not do that? The svn switch handles only the source files. The ppu files are created by you when you do 'make install'. And 'make install' does not uninstall any old ppu files.

Rigth. But the 'make install' do not override these files? If not, then is better delete all .ppu files in all directory?

Marcos Douglas

Reply by email

Marcos Douglas
to Marcos Douglas
Marcos Douglas wrote
Rigth. But the 'make install' do not override these files? If not, then is better delete all .ppu files in all directory?

I deleted all ppu files. Now I have another error:

C:\freepascal\lazarus>make all OPT="-glw2"
make -C lcl all
make[1]: Entering directory `C:/freepascal/lazarus/lcl' c:/freepascal/binutils/i386-win32/rm.exe -f units/i386-win32/alllclunits.ppu c:/freepascal/binutils/i386-win32/gmkdir.exe -p units/i386-win32 c:/freepascal/fpc/bin/i386-win32/ppc386.exe -gl -Fu. -Fuforms -Fuwidgetset -Fiin clude -FE. -FUunits/i386-win32 -glw2 -di386 alllclunits.pp Free Pascal Compiler version 2.4.1 [2010/06/07] for i386 Copyright (c) 1993-2009 by Florian Klaempfl
Target OS: Win32 for i386
Compiling alllclunits.pp
Compiling lclversion.pas
Compiling lclstrconsts.pas
Writing Resource String Table file: lclstrconsts.rst Compiling fpcadds.pas
Compiling lazlinkedlist.pas
Compiling dynhasharray.pp
Compiling lclproc.pas
Compiling avglvltree.pas
Compiling fileutil.pas
Compiling masks.pas
Fatal: Can't find unit Contnrs used by Masks
Fatal: Compilation aborted
make[1]: *** [alllclunits.ppu] Error 1
make[1]: Leaving directory `C:/freepascal/lazarus/lcl' make: *** [lcl] Error 2

Is better to get a clean branch of FPC 2.4.1?

Marcos Douglas

Reply by email

Mattias Gärtner
to Marcos Douglas

Zitat von Marcos Douglas :

Show quoted text 9 lines
On Mon, Jun 7, 2010 at 11:22 AM, Marcos Douglas wrote: > > Rigth. But the 'make install' do not override these files? If not, > then is better delete all .ppu files in all directory? > I deleted all ppu files. Now I have another error: C:\freepascal\lazarus>make all OPT="-glw2"

Always try "clean":

make clean all OPT="-glw2"

Mattias

Show quoted text 38 lines
make -C lcl all make[1]: Entering directory `C:/freepascal/lazarus/lcl' c:/freepascal/binutils/i386-win32/rm.exe -f units/i386-win32/alllclunits.ppu c:/freepascal/binutils/i386-win32/gmkdir.exe -p units/i386-win32 c:/freepascal/fpc/bin/i386-win32/ppc386.exe -gl -Fu. -Fuforms -Fuwidgetset -Fiin clude -FE. -FUunits/i386-win32 -glw2 -di386 alllclunits.pp Free Pascal Compiler version 2.4.1 [2010/06/07] for i386 Copyright (c) 1993-2009 by Florian Klaempfl Target OS: Win32 for i386 Compiling alllclunits.pp Compiling lclversion.pas Compiling lclstrconsts.pas Writing Resource String Table file: lclstrconsts.rst Compiling fpcadds.pas Compiling lazlinkedlist.pas Compiling dynhasharray.pp Compiling lclproc.pas Compiling avglvltree.pas Compiling fileutil.pas Compiling masks.pas Fatal: Can't find unit Contnrs used by Masks Fatal: Compilation aborted make[1]: *** [alllclunits.ppu] Error 1 make[1]: Leaving directory `C:/freepascal/lazarus/lcl' make: *** [lcl] Error 2 Is better to get a clean branch of FPC 2.4.1? Marcos Douglas -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
------------------ Powered by NetMail

Reply by email

waldo kitty
to Mattias Gärtner: Zitat von Marcos Douglas : The svn switch handles only the source files. The ppu files…
Mattias G?rtner wrote 12 lines
Zitat von Marcos Douglas : > 2010/6/7 Mattias G?rtner : >> But you have to make sure that the FPC installation is not mixed. >> That means before you install FPC into a directory, delete the >> units directory. > > First I compiled FPC 2.5.1. But now, I change to 2.4.1 and compiled. > The command "Switch", in SVN, not do that? The svn switch handles only the source files. The ppu files are created by you when you do 'make install'. And 'make install' does not uninstall any old ppu files.

ahhh... so somewhere there must be something like

cd \fpcdirectory
del /s *.ppu

which walks each of the directories within \fpcdirectory and deletes all .ppu files?? any others? .o files??

Reply by email

Marcos Douglas
to waldo kitty

2010/6/7 Mattias G?rtner :

Always try "clean": make clean all OPT="-glw2"

Ok, I will try.

waldo kitty wrote 8 lines
ahhh... so somewhere there must be something like ?cd \fpcdirectory ?del /s *.ppu which walks each of the directories within \fpcdirectory and deletes all .ppu files?? any others? .o files??

Well, I will try 'clean' now... this parameter should do this cleaning.

Marcos Douglas

Reply by email

waldo kitty
to Mattias Gärtner: Zitat von Marcos Douglas : Always try "clean": make clean all OPT="-glw2" Mattias…
Mattias G?rtner wrote 15 lines
Zitat von Marcos Douglas : > On Mon, Jun 7, 2010 at 11:22 AM, Marcos Douglas wrote: >> >> Rigth. But the 'make install' do not override these files? If not, >> then is better delete all .ppu files in all directory? >> > > I deleted all ppu files. Now I have another error: > > C:\freepascal\lazarus>make all OPT="-glw2" Always try "clean": make clean all OPT="-glw2"

i've been noticing that it seems that locating that Contnrs unit is a real buggar... the bad ppu was that one and now that the ppus are gone, this one unit's sources are not found? is this where killing the .o files is needed or does "clean" kill the .ppus and .os?

Show quoted text 46 lines
Mattias > make -C lcl all > make[1]: Entering directory `C:/freepascal/lazarus/lcl' > c:/freepascal/binutils/i386-win32/rm.exe -f > units/i386-win32/alllclunits.ppu > c:/freepascal/binutils/i386-win32/gmkdir.exe -p units/i386-win32 > c:/freepascal/fpc/bin/i386-win32/ppc386.exe -gl -Fu. -Fuforms > -Fuwidgetset -Fiin > clude -FE. -FUunits/i386-win32 -glw2 -di386 alllclunits.pp > Free Pascal Compiler version 2.4.1 [2010/06/07] for i386 > Copyright (c) 1993-2009 by Florian Klaempfl > Target OS: Win32 for i386 > Compiling alllclunits.pp > Compiling lclversion.pas > Compiling lclstrconsts.pas > Writing Resource String Table file: lclstrconsts.rst > Compiling fpcadds.pas > Compiling lazlinkedlist.pas > Compiling dynhasharray.pp > Compiling lclproc.pas > Compiling avglvltree.pas > Compiling fileutil.pas > Compiling masks.pas > Fatal: Can't find unit Contnrs used by Masks > Fatal: Compilation aborted > make[1]: *** [alllclunits.ppu] Error 1 > make[1]: Leaving directory `C:/freepascal/lazarus/lcl' > make: *** [lcl] Error 2 > > Is better to get a clean branch of FPC 2.4.1? > > > Marcos Douglas > > -- > _______________________________________________ > Lazarus mailing list > > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus >

Reply by email

Marcos Douglas
to waldo kitty
waldo kitty wrote 9 lines
> > Always try "clean": > > make clean all OPT="-glw2" i've been noticing that it seems that locating that Contnrs unit is a real buggar... the bad ppu was that one and now that the ppus are gone, this one unit's sources are not found? is this where killing the .o files is needed or does "clean" kill the .ppus and .os?

I do know yet. In a couple minutes I will to try 'make clean all...'

Marcos Douglas

Reply by email

Marcos Douglas
to Marcos Douglas
Marcos Douglas wrote 13 lines
On Mon, Jun 7, 2010 at 2:02 PM, waldo kitty wrote: >> >> Always try "clean": >> >> make clean all OPT="-glw2" > > i've been noticing that it seems that locating that Contnrs unit is a real > buggar... the bad ppu was that one and now that the ppus are gone, this one > unit's sources are not found? is this where killing the .o files is needed > or does "clean" kill the .ppus and .os? I do know yet. In a couple minutes I will to try 'make clean all...'

ERROR:
Fatal: Can't find unit Contnrs used by Masks
Fatal: Compilation aborted
make[1]: *** [alllclunits.ppu] Error 1
make[1]: Leaving directory `C:/freepascal/lazarus/lcl' make: *** [lcl] Error 2

Maybe 'make clean all' do not delete all generated got all files at SVN, again, for FPC and Lazarus and now works.

...is better not put versions together ;-)

Marcos Douglas

Reply by email

Marco van de Voort
to waldo kitty: i've been noticing that it seems that locating that Contnrs unit is a real buggar... the…
waldo kitty wrote 8 lines
> Always try "clean": > > make clean all OPT="-glw2" i've been noticing that it seems that locating that Contnrs unit is a real buggar... the bad ppu was that one and now that the ppus are gone, this one unit's sources are not found? is this where killing the .o files is needed or does "clean" kill the .ppus and .os?

http://www.stack.nl/~marcov/buildfaq/#toc-Subsection-2.6.2

Reply by email

Marcos Douglas
to Marco van de Voort
Marco van de Voort wrote 12 lines
On Mon, Jun 07, 2010 at 01:02:48PM -0400, waldo kitty wrote: > > Always try "clean": > > > > make clean all OPT="-glw2" > > i've been noticing that it seems that locating that Contnrs unit is a real > buggar... the bad ppu was that one and now that the ppus are gone, this one > unit's sources are not found? is this where killing the .o files is needed or > does "clean" kill the .ppus and .os? http://www.stack.nl/~marcov/buildfaq/#toc-Subsection-2.6.2

Thanks Marco.
The problem was "mixing of FPC versions".

Marcos Douglas

Reply by email

Florian Klaempfl
to waldo kitty: i've been noticing that it seems that locating that Contnrs unit is a real buggar... the…
Show quoted text 19 lines
On 6/7/2010 11:11, Mattias G?rtner wrote: > Zitat von Marcos Douglas : > >> On Mon, Jun 7, 2010 at 11:22 AM, Marcos Douglas wrote: >>> >>> Rigth. But the 'make install' do not override these files? If not, >>> then is better delete all .ppu files in all directory? >>> >> >> I deleted all ppu files. Now I have another error: >> >> C:\freepascal\lazarus>make all OPT="-glw2" > > Always try "clean": > > make clean all OPT="-glw2" i've been noticing that it seems that locating that Contnrs unit is a real buggar...

This has nothing to do with contnrs in particular. It seems contnrs is only the first unit being searched and thus not found if your fpc setup is broken.

Reply by email

Marcos Douglas
to Marcos Douglas: Thanks Marco. The problem was "mixing of FPC versions". Marcos Douglas
Marcos Douglas wrote 17 lines
On Tue, Jun 8, 2010 at 5:07 AM, Marco van de Voort wrote: > On Mon, Jun 07, 2010 at 01:02:48PM -0400, waldo kitty wrote: >> > Always try "clean": >> > >> > make clean all OPT="-glw2" >> >> i've been noticing that it seems that locating that Contnrs unit is a real >> buggar... the bad ppu was that one and now that the ppus are gone, this one >> unit's sources are not found? is this where killing the .o files is needed or >> does "clean" kill the .ppus and .os? > > > http://www.stack.nl/~marcov/buildfaq/#toc-Subsection-2.6.2 Thanks Marco. The problem was "mixing of FPC versions".

This problem happend again... :(

I posted this: http://lists.lazarus.freepascal.org/pipermail/lazarus/2010-June/053304.html ...and now, when I try to build Lazarus, error: "Can't find unit Contnrs..."

If I get a clean FPC and Lazarus form SVN, this will works... But I ask: I can not update sources after obtaining a "stable version" at SVN??

Thanks,
Marcos Douglas

Reply by email

Marcos Douglas
to Marcos Douglas
Marcos Douglas wrote 8 lines
This problem happend again... ?:( I posted this: http://lists.lazarus.freepascal.org/pipermail/lazarus/2010-June/053304.html ...and now, when I try to build Lazarus, error: "Can't find unit Contnrs..." If I get a clean FPC and Lazarus form SVN, this will works... But I ask: I can not update sources after obtaining a "stable version" at SVN??

Hi,
I need help, PLEASE.

After to get all files of SVN (FPC and Lazarus) it doesn't works. I can not compile Lazarus anymore.
Below the ERROR:
(...)
Compiling interfacebase.pp
Compiling lclintf.pas
Compiling lresources.pp
Compiling lazconfigstorage.pas
lresources.pp(5320,13) Error: Incompatible types: got "AnsiString" expected "Cha r"
lresources.pp(5514) Fatal: There were 1 errors compiling module, stopping Fatal: Compilation aborted
make[1]: *** [alllclunits.ppu] Error 1
make[1]: Leaving directory `C:/freepascal/laz/0.9.28/lcl' make: *** [lcl] Error 2

C:\freepascal\laz\0.9.28>
_________________________________

...now, I will explain all steps I did:

1- Create c:\freepascal | c:\freepascal\binutils | c:\freepascal\fpc\2.4.1 | c:\freepascal\laz\0.9.28 2- In c:\freepascal\binutils I put ppc386.exe and fpc.cfg 3- In c:\freepascal\binutils I got from SVN:
\arm-wince = http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_4/install/crossbinwce \i386-win32 = http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_4/install/binw32 \x86_64-win64 =
http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_4/install/binw64 4- In <fpc>\2.4.1\
I got from SVN: http://svn.freepascal.org/svn/fpc/branches/fixes_2_4 5- In <laz>\0.9.28\
I got from SVN: http://svn.freepascal.org/svn/lazarus/branches/fixes_0_9_28 6- In c:\freepascal\ i have the build-fpc.bat:
@echo on

set fpc_ver=c:\freepascal\fpc\2.4.1\

set path=c:\freepascal\binutils\i386-win32;c:\freepascal\binutils\x86_64-win64;c:\freepascal\binutils\arm-wince;%fpc_ver%utils\fpcm;%fpc_ver%bin\i386-win32;%path%

cd c:\freepascal\fpc\2.4.1\

make distclean OS_TARGET=win32 CPU_TARGET=i386
FPC=c:\freepascal\binutils\ppc386.exe
make distclean OS_TARGET=win64 CPU_TARGET=x86_64
FPC=c:\freepascal\binutils\ppc386.exe
make distclean OS_TARGET=wince CPU_TARGET=arm
FPC=c:\freepascal\binutils\ppc386.exe

make clean all install INSTALL_PREFIX=%fpc_ver%
FPC=c:\freepascal\binutils\ppc386.exe

make clean all crossinstall OS_TARGET=win64 CPU_TARGET=x86_64 UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=%fpc_ver%
make clean all crossinstall OS_TARGET=wince CPU_TARGET=arm UPXPROG=echo OPT="-glw2" INSTALL_PREFIX=%fpc_ver%
BINUTILSPREFIX=arm-wince-

7- ... and I have the build-laz.bat:
@echo on

set fpc_ver=c:\freepascal\fpc\2.4.1\

set path=c:\freepascal\binutils\i386-win32;c:\freepascal\binutils\x86_64-win64;c:\freepascal\binutils\arm-wince;%fpc_ver%utils\fpcm;%fpc_ver%bin\i386-win32;%path%

cd c:\freepascal\laz\0.9.28\

make distclean
make clean all OPT="-glw2"

8- I put in PATH:
C:\freepascal\binutils;C:\freepascal\fpc\2.4.1\bin\i386-win32;%path%

9- I compiled FPC (in prompt: c:\freepascal\build-fpc.bat)

10- ERROR (above) to try compile Lazarus (in prompt: c:\freepascal\build-laz.bat)

Now, my fpc.cfg (in c:\freepascal\binutils)

#
# Config file generated by fpcmkcfg on 31/05/2010 - 17:12:13 # Example fpc.cfg for Free Pascal Compiler
#

# ----------------------
# Defines (preprocessor)
# ----------------------

#
# nested #IFNDEF, #IFDEF, #ENDIF, #ELSE, #DEFINE, #UNDEF are allowed #
# -d is the same as #DEFINE
# -u is the same as #UNDEF
#

#
# Some examples (for switches see below, and the -? helppages) #
# Try compiling with the -dRELEASE or -dDEBUG on the commandline #

# For a release compile with optimizes and strip debuginfo #IFDEF RELEASE
-O2
-Xs
#WRITE Compiling Release Version
#ENDIF

# For a debug version compile with debuginfo and all codegeneration checks on #IFDEF DEBUG
-glh
-Crtoi
#WRITE Compiling Debug Version
#ENDIF

# ----------------
# Parsing switches
# ----------------

# Pascal language mode
# -Mfpc free pascal dialect (default)
# -Mobjfpc switch some Delphi 2 extensions on # -Mdelphi tries to be Delphi compatible
# -Mtp tries to be TP/BP 7.0 compatible # -Mgpc tries to be gpc compatible
# -Mmacpas tries to be compatible to the macintosh pascal dialects #
# Turn on Object Pascal extensions by default
#-Mobjfpc

# Assembler reader mode
# -Rdefault use default assembler
# -Ratt read AT&T style assembler
# -Rintel read Intel style assembler
#
# All assembler blocks are AT&T styled by default
#-Ratt

# Semantic checking
# -S2 same as -Mobjfpc
# -Sc supports operators like C (*=,+=,/= and -=) # -Sa include assertion code.
# -Sd same as -Mdelphi
# -Se<x> compiler stops after the <x> errors (default is 1) # -Sg allow LABEL and GOTO
# -Sh Use ansistrings
# -Si support C++ styled INLINE
# -SI<x> set interface style to <x>
# -SIcomCOM compatible interface (default) # -SIcorbaCORBA compatible interface
# -Sm support macros like C (global)
# -So same as -Mtp
# -Sp same as -Mgpc
# -Ss constructor name must be init (destructor must be done) # -St allow static keyword in objects
#
# Allow goto, inline, C-operators, C-vars
-Sgic

# ---------------
# Code generation
# ---------------

# Uncomment the next line if you always want static/dynamic units by default # (can be overruled with -CD, -CS at the commandline) #-CS
#-CD

# Set the default heapsize to 8Mb
#-Ch8000000

# Set default codegeneration checks (iocheck, overflow, range, stack) #-Ci
#-Co
#-Cr
#-Ct

# Optimizer switches for i386 compiler
# -Os generate smaller code
# -O1 level 1 optimizations (quick optimizations) # -O2 level 2 optimizations (-O1 + slower optimizations) # -O3 level 3 optimizations (same as -O2u)
# -Oa=N set alignment to N
# -OoX switch on optimalization X.
# -OoNOX switch off optimalization X.
# X is one of REGVAR UNCERTAIN STACKFRAME PEEPHOLE ASMCSE LOOPUNROLL
# -OpCPU set target processor.
# CPU is one of 386, PENTIUM, PENTIUM2, PENTIUM3, PENTIUM4, PENTIUMM

# -----------------------
# Set Filenames and Paths
# -----------------------

# Both slashes and backslashes are allowed in paths

# path to the messagefile, not necessary anymore but can be used to override # the default language
#-FrC:\freepascal\fpc/$FPCVERSION/msg/errore.msg
#-FrC:\freepascal\fpc/$FPCVERSION/msg/errorn.msg
#-FrC:\freepascal\fpc/$FPCVERSION/msg/errores.msg
#-FrC:\freepascal\fpc/$FPCVERSION/msg/errord.msg
#-FrC:\freepascal\fpc/$FPCVERSION/msg/errorr.msg

# path to the gcclib
#-FlC:\freepascal\fpc/$FPCVERSION/lib

#IFDEF FPCAPACHE_1_13
-FuC:\freepascal\fpc/$FPCVERSION/units/$FPCTARGET/httpd13/ #ELSE
#IFDEF FPCAPACHE_2_0
-FuC:\freepascal\fpc/$FPCVERSION/units/$FPCTARGET/httpd20 #ELSE
-FuC:\freepascal\fpc/$FPCVERSION/units/$FPCTARGET/httpd22 #ENDIF
#ENDIF

# searchpath for units and other system dependent things -FuC:\freepascal\fpc/$FPCVERSION/units/$FPCTARGET/ -FuC:\freepascal\fpc/$FPCVERSION/units/$FPCTARGET/* -FuC:\freepascal\fpc/$FPCVERSION/units/$FPCTARGET/rtl

# searchpath for libraries
#-FlC:\freepascal\fpc/$FPCVERSION/lib
#-Fl/lib;/usr/lib

# searchpath for tools
-FDC:\freepascal\fpc/$FPCVERSION/bin/$FPCTARGET

# binutils prefix for cross compiling
#IFDEF FPC_CROSSCOMPILING
-XP$FPCTARGET-
#ENDIF

# -------------
# Linking
# -------------

# generate always debugging information for GDB (slows down the compiling # process)
# -gc generate checks for pointers
# -gd use dbx
# -gg use gsym
# -gh use heap trace unit (for memory leak debugging) # -gl use line info unit to show more info for backtraces # -gv generates programs tracable with valgrind # -gw generate dwarf debugging info
#
# Enable debuginfo and use the line info unit by default #-gl

# always pass an option to the linker
#-k-s

# Always strip debuginfo from the executable
-Xs

# -------------
# Miscellaneous
# -------------

# Write always a nice FPC logo ;)
-l

# Verbosity
# e : Show errors (default) d : Show debug info # w : Show warnings u : Show unit info # n : Show notes t : Show tried/used files # h : Show hints m : Show defined macros # i : Show general info p : Show compiled procedures # l : Show linenumbers c : Show conditionals # a : Show everything 0 : Show nothing (except errors) # b : Show all procedure r : Rhide/GCC compatibility mode # declarations if an error x : Executable info (Win32 only) # occurs
#
# Display Info, Warnings, Notes and Hints
-viwn
# If you don't want so much verbosity use
#-vw

So, what I can do? :((((

Thanks,
Marcos Douglas

Reply by email