Hi,
My env is WinXP (3 bits, of course), FPC 2.5.1 (/branches_2_6) and Lazarus 0.9.31.
I have FPC and Lazarus working on my notebook and I have a HD external too (in any PC I can use the FPC/Lazarus, just using --pcp to start it).

Now I have to compile a console program (this is the first) to use in a Win7 64bits dual core.

My questions are:
1. I can use Lazarus 32bits in a machine 64bits but compile a program to 64bits?
2. The make, to compile FPC, knows about if the machine is 64bits or I have to type a parameter?

[1] http://wiki.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29

Marcos Douglas

I never used PATH to compile or use them.
First I'm trying to compile FPC in a Win7 64bits.
I use this script[1] to compile FPC 32bit with success. So, I changed the script to:

set myVERSION=2.7.1
set myROOT=c:\freepascal
set myFPC=%myROOT%\compiler\%myVERSION%
set myBINUTILS=%myROOT%\binutils
set PATH=%myBINUTILS%\x86_64-win64;%myFPC%\bin\i386-win32

cd %myFPC%

make clean all install OS_TARGET=win64 CPU_TARGET=x86_64 INSTALL_PREFIX=%myFPC% PP=%myBINUTILS%\ppc386.exe
DATA2INC=%myFPC%\utils\data2inc.exe

As you can see, I only includes: OS_TARGET=win64 CPU_TARGET=x86_64 parameters.

Question:
I can compile a new fpc.exe to 64bit using a ppc386.exe 32bit version, on a machine 64bit?

[1] http://wiki.freepascal.org/Installing_Lazarus#Compiling.2Finstalling_FPC_and_Lazarus_from_Sources_of_SVN_.28Win32.29

Marcos Douglas

Marcos Douglas

2011/8/19 Marcos Douglas :

Yes, that is possible. Even on a 32 bits machine you can compile a program to 64 bits. It is called cross compiling.

2. The make, to compile FPC, knows about if the machine is 64bits or I have to type a parameter?

Set the target processor and the target OS in Lazarus.

For more details on compiling the fpc units for win64, see the buildfaq. www.stack.nl/~marcov/buildfaq.pdf

Vincent

My questions are: 1. I can use Lazarus 32bits in a machine 64bits but compile a program to 64bits? 2. The make, to compile FPC, knows about if the machine is 64bits or I have to type a parameter?

I encountered many problems, in compiling 64 bit applications on a 64 bit Windows. One problem is the bad guess of fpc.exe, to build for 32 bit by default. More problems result from the tools in the fpc/bin directory, whose 32 and 64 bit versions have the same name. This discourages to have the fpc/bin directory in the PATH, in contrast to the default FPC/Lazarus installation. Finally the debugger seems to have problems with 32 and 64 bit applications (this may have changed in the meantime).

For building FPC I replace the PATH entirely by the appropriate fpc/bin directory, which contains all required tools (what is not guaranteed by the standard installation). It may be a good idea to have isolated accounts, containing the 32/64 bit installations of FPC and Lazarus.

DoDi

Question: I can compile a new fpc.exe to 64bit using a ppc386.exe 32bit version, on a machine 64bit?

Yes and no ;-)

Yes, you can create an ppcrossx64.exe, along with the 64 bit libraries, using ppc386.exe.

No, fpc.exe doesn't compile anything itself, it only calls the compiler for the selected target.

DoDi

The point is that a fpc.exe compiled for 32bit will select the 32bit compiler (ppcx86) as default while the one compiled for 64bit will select the 64bit compiler as default (ppcx64). So it does matter what platform you compile fpc.exe for.

Regards,
Sven

The point is that a fpc.exe compiled for 32bit will select the 32bit compiler (ppcx86) as default while the one compiled for 64bit will select the 64bit compiler as default (ppcx64). So it does matter what platform you compile fpc.exe for.

Thanks, this explains the strange behaviour of fpc.exe on 64 bit Windows. It seems to be required to have FPC and Lazarus installed in both 32 and 64 bit versions, in order to create and debug applications for both targets.

DoDi

Marcos Douglas wrote

My questions are: 1. I can use Lazarus 32bits in a machine 64bits but compile a program to 64bits?

I have long since given up on cross-compiling. And even when it did work (successfully generated an executable), that executable often crashed when run. So now I simply have one VM session for each OS we want to target. I have build scripts on each, so no need to open IDE's compile packages, change compiler settings for release versions etc. Simply load the VM, and run the build script. The build script automatically pulls the latest code and compiles with release build compiler settings.

This works perfectly for our company for over a year, and we will continue using this method in the future.

Sorry, do I need ppcrossx64.exe?
I do not want use cross-compile. I said I have two Windows versions: XP and 7. So, I want to use the same FPC/Lazarus code (hd external) and run a script in WinXP and create my app and, after run other script and create the same app, but to 64bit target.

I is not necessary to compile the app 64bit on Win32.

Marcos Douglas

So, to compile the first version of FPC 64 I have to download a ppcx64.exe and run make. Is that?

Marcos Douglas

This is my fear. Therefore I said that I will compile in each OS.

But you have a copy of FPC for each OS?
You can use different sources, no? I would like to use a only source (FPC and Lazarus) and scripts to compile for each OS (in my case, today, just do WinXP and Win7).

Marcos Douglas

I don't want to use cross compile. I want use a same code of FPC to compile in each OS.

I will see.

Marcos Douglas

fpc.exe is AFAIK only compiled if you run a "make install" or you run "make fpc" in the "compiler/utils" directory (not exactly sure about the last one).

Regards,
Sven

It depends on the OS: Win32/Win64 cross compilation works perfectly because
- of the internal linker
- dyn. libraries not needed at the linking stage
- lazier library dependencies
So it's not fpc's/lazarus's fault but a problem of the platform.

I didn't know that. Well... I always ran 'make install'.

I know the fpc.exe just calls ppc386.exe but what advantages to do this? Well, this is another thread...

Marcos Douglas

Marcos Douglas wrote

I know the fpc.exe just calls ppc386.exe but what advantages to do this?

Regardless of the target processor, it's enough just to call fpc to get an executable for the current platform.

Oh, I did know that. Thanks.

Way up in this thread you presented your installation script. Did you ever use it? It looks as if you only ask, and never try to run any of your or other people suggestions.

What? Of course I use it!
I didn't understand you did you mean... could you explain? This script works to Win32...

BTW, the simplest way to install fpc on Windows is using an snapshot: http://www.hu.freepascal.org/lazarus/

I install my FPC and Lazarus using the script did you talk about. Only using SVN.

Marcos Douglas

I know the fpc.exe just calls ppc386.exe but what advantages to do this? Well, this is another thread...

fpc doesn't "just call", it calls the compiler for the given target. ppc386 may ignore the target options, or complain about a non-Win32 target.

Way up in this thread you presented your installation script. Did you ever use it? It looks as if you only ask, and never try to run any of your or other people suggestions.

BTW, the simplest way to install fpc on Windows is using an snapshot: http://www.hu.freepascal.org/lazarus/

DoDi

The fpc.exe calls the ppcXXX for each target?

BTW, look the attachment. Why there is a some exe files in these paths? IMHO, Isn't better that each binary stay in \i386-win32 or \x86_64-win64 directories, for example?

I can use a single FPC source to work with two processors targets? The binaries above will be replaced when I compile the last time?

Marcos Douglas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: printscreen.jpg
Type: image/jpeg
Size: 54368 bytes
Desc: not available
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110820/24db9553/attachment-0001.jpg>

Could you explain more about how do you works with scripts? For example, how do you updates ALL script if you add one more lib (sources)?
Do you have a FPC and Lazarus installed in each VM?

Marcos Douglas