Forum > Other OS
BUG REPORT: Unable to generate DEB/RPM/TAR installation package from FPC source
PascalDragon:
--- Quote from: gasensor on April 17, 2024, 05:10:20 pm ---Unable to submit ISSUS for FPP_BUILD on Gitlab.
--- End quote ---
It seems that issues aren't enabled for that project. I've now asked the project manager what to do.
--- Quote from: gasensor on April 17, 2024, 05:10:20 pm ---Before the official release of the software, regular/basic functions must be tested.
--- End quote ---
The FPC Build repository is not normally used by endusers. It's used by the release engineers to generate the releases that the end users will use and there testing is part of the release engineering.
--- Quote from: gasensor on April 17, 2024, 05:10:20 pm ---Gitlab is not easy to use.
--- End quote ---
That is just an excuse.
dbannon:
--- Quote from: gasensor on April 15, 2024, 11:12:23 am ---rpm: Failed make: *** There are no rules for making target "rpm". Stop it.
deb: Failed ! /usr/bin/echo "Debian version (3.2.0) is not correct, expect 3.2.2"
inno: Not available on Linux
innox64: Not available on Linux
--- End quote ---
Building debs, rpms and using inno all require quite specific software tools on your system. Do you already have those things ? Without them, no chance of a build working. I don't think there is any reason to think that the average FPC user, you or me, would be attempting to use those "make targets".
I imagine the necessary build environment is documented somewhere, but again, not something you would find with understanding the process.
Davo
gasensor:
--- Quote from: PascalDragon on April 18, 2024, 10:24:23 pm ---
--- Quote from: gasensor on April 17, 2024, 05:10:20 pm ---Unable to submit ISSUS for FPP_BUILD on Gitlab.
--- End quote ---
It seems that issues aren't enabled for that project. I've now asked the project manager what to do.
--- Quote from: gasensor on April 17, 2024, 05:10:20 pm ---Before the official release of the software, regular/basic functions must be tested.
--- End quote ---
The FPC Build repository is not normally used by endusers. It's used by the release engineers to generate the releases that the end users will use and there testing is part of the release engineering.
--- Quote from: gasensor on April 17, 2024, 05:10:20 pm ---Gitlab is not easy to use.
--- End quote ---
That is just an excuse.
--- End quote ---
FPC has not provided crossinstall installation package since 3.2.0, and users can only find their own way to solve it. This is a big problem for cross-platform embedded development. You can take a look at what I wrote: <Tutorial: Developing STM32F1 Programs with FPC/Lazarus/STLINK in Linux(Detailed)>. It's just too cumbersome.
https://forum.lazarus.freepascal.org/index.php/topic,66903.0.html
All you need to avoid all this is a separate installation package for embedded. And that's what I want to do. So I tried to DIY and found all sorts of problems. In particular, the installation system is different from the common C environment.
gasensor:
--- Quote from: dbannon on April 19, 2024, 06:29:49 am ---
--- Quote from: gasensor on April 15, 2024, 11:12:23 am ---rpm: Failed make: *** There are no rules for making target "rpm". Stop it.
deb: Failed ! /usr/bin/echo "Debian version (3.2.0) is not correct, expect 3.2.2"
inno: Not available on Linux
innox64: Not available on Linux
--- End quote ---
Building debs, rpms and using inno all require quite specific software tools on your system. Do you already have those things ? Without them, no chance of a build working. I don't think there is any reason to think that the average FPC user, you or me, would be attempting to use those "make targets".
I imagine the necessary build environment is documented somewhere, but again, not something you would find with understanding the process.
Davo
--- End quote ---
As far as I know, dpkg/rpm (rpmbuild) needs to be installed. However, the error message does not provide sufficient/correct information
Navigation
[0] Message Index
[*] Previous page