TOPIC:

In "Project Options", I have set "TargetOS" to "Win32" and "Target CPU Family" to "i386".

When I try to build, I get:
Compile package adFCL 6.3.1: Success
Compile package bs_Utils 6.3.1: Success, Hints: 17
lazutf8.pas(509,44) Hint: Mixing signed expressions and longwords gives a 64bit result
lazutf8.pas(519,53) Hint: Mixing signed expressions and longwords gives a 64bit result
lazutf8.pas(524,33) Hint: Mixing signed expressions and longwords gives a 64bit result
lazutf8.pas(530,44) Hint: Mixing signed expressions and longwords gives a 64bit result
lazfileutils.pas(108,71) Hint: Parameter "Rights" not used
compwriterpas.pas(1330,21) Hint: Mixing signed expressions and longwords gives a 64bit result
compwriterpas.pas(1330,21) Hint: Converting the operands to "Int64" before doing the multiply could prevent overflow errors.
compwriterpas.pas(1335,32) Hint: Mixing signed expressions and longwords gives a 64bit result
lazlistclasses.pas(1236,43) Hint: Mixing signed expressions and longwords gives a 64bit result
lazlistclasses.pas(1639,20) Hint: Mixing signed expressions and longwords gives a 64bit result
lazlistclasses.pas(501,126) Hint: Mixing signed expressions and longwords gives a 64bit result
lazlistclasses.pas(611,116) Hint: Mixing signed expressions and longwords gives a 64bit result
lazlistclasses.pas(652,71) Hint: Mixing signed expressions and longwords gives a 64bit result
lazlistclasses.pas(654,143) Hint: Mixing signed expressions and longwords gives a 64bit result
lazlistclasses.pas(799,27) Hint: Mixing signed expressions and longwords gives a 64bit result
lazlistclasses.pas(1236,43) Hint: Mixing signed expressions and longwords gives a 64bit result
lazlistclasses.pas(1639,20) Hint: Mixing signed expressions and longwords gives a 64bit result
Compile package adLCLBase 6.3.1: Exit code 1, Errors: 1, Warnings: 1
Warning: windres: can't open file `TCalendarPopupForm': No such file or directory
calendarpopup.pas(183,1) Error: Error while compiling resources -> Compile with -vd for more details. Check for duplicates.

The project is just a test project, it contains a TVirtualStringTree and a button.

Any project for test, Sir

So sorry for the long delay. Here's a ZIP file with my test project.

Thanks Sir
just uncheck
"Use additional compiler config file..."

Thank you, but unfortunately that didn't change anything for me.

Could the reason be a mistake I made in CT Center ?

I don't know
but
my suggestion is to "Remove and Build All" from CTCenter

I have now done so, but unfortunately the problem remains unchanged.

I'm attaching a screenshot showing my CTC.

Sir
Did you have any FPC or Lazarus Installations in your PC ?

We want more info
Please, post here your PC "Path" string only



.

Thank you Sternas,

I indeed had a Lazarus installation, plus some Embarcadero leftovers. I removed all of that, but now I'm getting:

Compile package adFCL 6.3.1: Exit code 1, Errors: 1
Error: ppc386.exe can't be executed, error message: Failed to execute ""ppc386.exe" -B -Twin32 -MObjFPC -Scghi -O1 -g -gl -l -vewnhibq -FuC:\codetyphon\typhon\packager\registration\ -FUC:\codetyphon\typhon\packager\units\i386-win32\ fcllaz.pas

The CTC "Get System Info" aborts (the output window closes after a split second).

For your Path
please go to CTCenter=>CommandBox page
to see the "Get System Info" result

Please Build FPC32
and post here the Action Log info (please zip first)

We try to get more information to help you...

After adding "C:\codetyphon\fpc\fpc32\bin\i386-win32" to my path, ppc386.exe now executes and I can build and launch my project.

Is this normal ?

Correction: I can only launch it without the debugger.

Here is the system info output:

I'm compiling fpc32 now.

I have now re-built fpc32.exe, build output is attached.

I still cannot debug though, but maybe that is normal when cross-compiling ?

Building still only works when ../fpc32/bin/i386-win32/ is in the path.

I could probably work like this, even though I cannot debug directly.

Is there a way to have a project with separate "configurations", one for 64-bit, one for 32-bit ?

<<I still cannot debug though, but maybe that is normal when cross-compiling ?>>

Yes you must use gdb for win32 target : C:\codetyphon\binGDB\win32\gdb.exe

and

gdb for win64 target : C:\codetyphon\binGDB\win64\gdb.exe

That works, thank you.

Are you considerung extending the IDE options so that a different debugger could be configured for each target platform ?

No yet Sir