On 2020-07-05 at 12:26, Joan Moreau wrote: > Ok, I tried to put a Makefile that import all needed packages > dynamically (via "git clone" mostly) Sorry - accessing the network during compilation is (at least generally) prohibited. IIRC, it both is a violation of Debian policy, and may actually not work from the build environment on the servers. You need to arrange for the relevant code to already be present prior to the start of the compilation process. > You may check > https://github.com/grosjo/tomboy-reborn/blob/master/packages/tomboy-reborn_1.0.0-1_amd64.deb That's a .deb file, which is a binary package. We need to look at the updated source package, which is used for generating the binary package. Looking at https://github.com/grosjo/tomboy-reborn, and more specifically at https://github.com/grosjo/tomboy-reborn/blob/master/packages/Makefile, I see that you're cloning two git repositories. If the software in those repositories is already packaged for Debian, you need to find out which packages it's in, add them as build-dependencies (as defined in some of the documents you've previously been linked to), and adjust your project (possibly through flags in the Makefile or appropriate setup in debian/rules) to draw on the files installed by those packages. If the software in those repositories is not already packaged for Debian, then unless an exception is allowed for, you need to get it packaged - into separate packages, not into the one you're already working on - and then do the above. If compiling your project needs the code from these repositories, how does your IDE-based build normally pick up that code? I'd expect that the same process should work for a command-line build, but I'll admit that I'm not familiar with Lazarus. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature