Re: [Qbs] Deployment and dependency bundling

2020-01-01 Thread Oswald Buddenhagen
On Sat, Dec 28, 2019 at 08:45:26PM +0300, Alberto Mardegan wrote: On 27/12/19 21:24, Oswald Buddenhagen wrote: "deployment" (you actually mean dependency embedding) is just a special form of "linking" dependencies. you should be able to make a fully static build or a bundle with embedded dlls a

Re: [Qbs] Deployment and dependency bundling

2019-12-28 Thread Alberto Mardegan
Ho Oswald, On 27/12/19 21:24, Oswald Buddenhagen wrote: > you're mixing up two separate issues. > > "deployment" (you actually mean dependency embedding) is just a special > form of "linking" dependencies. you should be able to make a fully > static build or a bundle with embedded dlls and plugin

Re: [Qbs] Deployment and dependency bundling

2019-12-28 Thread Richard Weickelt
> I've got it working to some point by adding these properties to the Rule: > > inputsFromDependencies: ["application", "dynamiclibrary"] > multiplex: true > outputFileTags: ["deployed_library"] > > but this causes the Rule to be run only for the application's > dependencies, and not

Re: [Qbs] Deployment and dependency bundling

2019-12-27 Thread Oswald Buddenhagen
On Fri, Dec 27, 2019 at 06:04:08PM +0300, Alberto Mardegan wrote: I agree that in many cases the Depends item is the one who has the best information on how to handle its deployment. For example, the QtGui module will know which platform plugins need to be deployed, and the QtQml module could kno

Re: [Qbs] Deployment and dependency bundling

2019-12-27 Thread Alberto Mardegan
On 27/12/19 15:15, Oswald Buddenhagen wrote: > dependency embedding should be a property of the Depends item (based on > https://bugreports.qt.io/browse/QBS-585). the way this is actually > handled is platform-dependent and needs to be properly abstracted > (https://bugreports.qt.io/browse/QBS-229)

Re: [Qbs] Deployment and dependency bundling

2019-12-27 Thread Oswald Buddenhagen
On Mon, Dec 23, 2019 at 06:28:19PM +0300, Alberto Mardegan wrote: Or maybe my approach is totally off, and it would be better to implement dependency deployment as a Product (since, ultimately, one would use it to obtain a MacOS package, an AppImage or a MSI package?)? dependency embedding sho

Re: [Qbs] Deployment and dependency bundling

2019-12-23 Thread Alberto Mardegan
On 28/11/19 23:08, Alberto Mardegan wrote: > Whether one prepares macOS bundles, AppImage files of MSI installers, > one has to go through the dependency collection step, which is largely > similar for all platforms. To be more explicit, I'm referring to the > kind of job that on macOS is perform

[Qbs] Deployment and dependency bundling

2019-11-28 Thread Alberto Mardegan
Hi again :-) Whether one prepares macOS bundles, AppImage files of MSI installers, one has to go through the dependency collection step, which is largely similar for all platforms. To be more explicit, I'm referring to the kind of job that on macOS is performed by the macdeployqt tool, and that