OOOhhhhh.... I think I see now! So I submit a tarball with the source code, and a spec file with what it takes to build the code. Do I provide any other individual files such as COPYING or README or just the tarball and rpm spec? Am I the only one who missed that idea? How do I specify that I need the qt-devel version 4.x to the build the package? Does build service have all of the development packages on them by default? -joe On Tuesday 14 August 2007 08:05, Dirk Stoecker wrote:
On Tue, 14 Aug 2007, Joe Croft wrote:
Hi Peter,
What you save about packages and projects make sense. I actually keep the source in my CM separated like that and bring them together for the build. I guess this is what I need to know. When I want to build the packages using the build service, how do I specify the packages which go into the build?
Could it be that I'm just confused and all packages in a project get built in their respective directories to make a project? From the code, then can I reference the files something like "#include ../QcjData/QcjDataWidget.h"?
Are you mixing something here?
Normally you do not acces any .h or .c files in the build. Usually you have one or more .tar or.tar.gz files and a spec file. The .tar.gz contains the whole source tree including subdirectories, configure, makefiles and all that stuff.
The RPM build process extracts the source tarball, calls the makefiles (or whatever is required to build the packages), calls the install parts of the makefile and afterwards joins all the files/scripts/... into a RPM.
The BuildService is thus a meta-sourcecode repository, as here the tarballs containing the actual sources as well as patch files are the "source files" and the .spec files and related stuff are like the makefiles.
Or did I misinterpret your text above?
Ciao
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org