Mine has 1GB of RAM
I was looking at cross compilers available as part of the ubuntu stack. It is probably possible to build a version for the powerpc processor in the pipeline (travis.ci) Whether the code would run efficiently on a particular platform is a different issue.
@Peregrin4, Do you have one of the newer aluminum models?
Processor Speed: 1.42 GHz Processor Type: PowerPC 7447a (G4)
Video Card: Radeon 9200 VRAM Type: DDR SDRAM Details: ATI Radeon 9200 with 32 MB of DDR SDRAM (AGP 4X Support). Standard VRAM: 32 MB Maximum VRAM: 32 MB Display Support: Single Display Resolution Support: 1920x1200
Not sure this will be enough to run smoothly…
No, I wish. That would be a lot easier I suppose… Those are Intel based
I will. Thanks!
@Peregrin4 I did a search on “ubuntu toolchain powerpc”. I found several links you might want to follow up:
There are many others. I am not yet even close to an expert on this, but some understanding is required if you plan to do a local build with qtmake on any machine you have (probably not the powerpc) and also needs investigating before even attempting to build through a pipeline. I am starting to investigate the travis.ci service which allows a build to be done with a specified ubuntu configuration.
@Peregrin4 I don’t know whether you have pursued building Seamly on your G4 powerpc machine, but I thought of you today. With some other things I am doing, I stumbled over the fact that if you used a “little endian” cpu - which you do NOT - you would be able to have launchpad (part of the Ubuntu support structure) build you an executable. They have apparently dropped support for “big endian” versions due to lack of interested and competent participants. If you want to discuss little endian and big endian issues I can point you to some forums where people care. In some circles it is a religious issue.
Short answer is that you can probably find ideas or support if you dive deeply into ubuntu and launchpad and forums discussing same. Good luck with whatever you do.
I’m wondering if another option might be to use a VM. I’ve ended up doing that for a number of packages that aren’t available for Windows.
I’m sure that I’ll have the time and energy any century now!