Recent

Author Topic: Build FCP with WinCE crosscompiler from source under Linux  (Read 936 times)

dbannon

  • Hero Member
  • *****
  • Posts: 3556
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Build FCP with WinCE crosscompiler from source under Linux
« Reply #15 on: November 03, 2025, 11:47:40 pm »
Wow, thats a whole different story !

Milliuw, if you get that working, you are morally bound to document the process on the Wiki !

(Just think of what we'd loose if PascalDragon fell under that proverbial bus !)

Given what PD just said, I think I would -
  • Install FPC and FPC-SRC from repo. Thats 3.2.2
  • As root, run the commands he mentions.


As WinCE is so old, I doubt any new WinCE features  in main ....

Davo
Lazarus 3, Linux (and reluctantly Win10/11, OSX Monterey)
My Project - https://github.com/tomboy-notes/tomboy-ng and my github - https://github.com/davidbannon

PascalDragon

  • Hero Member
  • *****
  • Posts: 6184
  • Compiler Developer
Re: Build FCP with WinCE crosscompiler from source under Linux
« Reply #16 on: November 06, 2025, 08:40:13 pm »
  • Install FPC and FPC-SRC from repo. Thats 3.2.2
  • As root, run the commands he mentions.
Don't run the make all as root, only the make install (though even that isn't necessary if you install to a user writable location).

dbannon

  • Hero Member
  • *****
  • Posts: 3556
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Build FCP with WinCE crosscompiler from source under Linux
« Reply #17 on: Today at 12:44:36 am »
  • Install FPC and FPC-SRC from repo. Thats 3.2.2
  • As root, run the commands he mentions.
Don't run the make all as root, only the make install (though even that isn't necessary if you install to a user writable location).

If he has installed from the repo, and is using FPC322, then the FPC source will be in read only space, therefore to make anything there requires root. Building as root is certainly undesirable, but as PascalDragon greatly simplified the process and we determined slackware had FPC322 in its repo it seems like its the better approach.

If I was doing it, I would certainly -
  • Install FPC322 from the repo. That ends up in root space and brings required dependencies.
  • Download and untar FPC main source from gitlab into user space.
  • Use 322 to build and install main in user space, as per PD's instructions.
  • Edit .bashrc to add path to new fpc ahead of existing path, eg


export PATH=$USER/bin/FPC/fpc-main/bin;$PATH

and if using lazarus, manually point it to use the new FPC too.
 
Davo
Lazarus 3, Linux (and reluctantly Win10/11, OSX Monterey)
My Project - https://github.com/tomboy-notes/tomboy-ng and my github - https://github.com/davidbannon

 

TinyPortal © 2005-2018