Thread overview | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
June 17, 2017 Linking external *.lib files | ||||
---|---|---|---|---|
| ||||
Let's assume, I have the following 2 dub packages: pkgBASE: source/ lib/ pkgAPP: |
June 17, 2017 Re: Linking external *.lib files | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jolly James | Let's assume, I have the following 2 dub packages: pkgBASE: (depends on public DUB package) source/ lib/ pkgAPP: (depends on pkgBASE) source/ I have added pkgBASE via add-path. This wasn't a problem at all. Unfortunately, the public DUB package requires to be linked with the libs from pkgBASE/lib. What do I have to add to pkgBASE's dub.json? |
June 17, 2017 Re: Linking external *.lib files | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jolly James | On Saturday, 17 June 2017 at 00:09:41 UTC, Jolly James wrote:
> Let's assume, I have the following 2 dub packages:
>
>
> pkgBASE:
> (depends on public DUB package)
> source/
> lib/
> pkgAPP:
> (depends on pkgBASE)
> source/
>
>
> I have added pkgBASE via add-path. This wasn't a problem at all.
>
> Unfortunately, the public DUB package requires to be linked with the libs from pkgBASE/lib. What do I have to add to pkgBASE's dub.json?
Side-note: the lib/ should not be moved for portability reasons if this is possible
|
June 17, 2017 Re: Linking external *.lib files | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jolly James | On Saturday, 17 June 2017 at 00:33:01 UTC, Jolly James wrote:
> On Saturday, 17 June 2017 at 00:09:41 UTC, Jolly James wrote:
>> Let's assume, I have the following 2 dub packages:
>>
>>
>> pkgBASE:
>> (depends on public DUB package)
>> source/
>> lib/
>> pkgAPP:
>> (depends on pkgBASE)
>> source/
>>
>>
>> I have added pkgBASE via add-path. This wasn't a problem at all.
>>
>> Unfortunately, the public DUB package requires to be linked with the libs from pkgBASE/lib. What do I have to add to pkgBASE's dub.json?
>
> Side-note: the lib/ should not be moved for portability reasons if this is possible
My bad solution:
"lflags": [
"-Llib\\"
],
but this requires the lib folder to be part of pkgAPP, not pkgBASE where I would like to have it. Does anyone have an idea?
|
June 21, 2017 Re: Linking external *.lib files | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jolly James | *push* |
June 21, 2017 Re: Linking external *.lib files | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jolly James | On Wednesday, 21 June 2017 at 13:07:31 UTC, Jolly James wrote: > *push* Have you asked on the Dub forum? http://forum.rejectedsoftware.com/groups/rejectedsoftware.dub/ |
June 21, 2017 Re: Linking external *.lib files | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jolly James | On Saturday, 17 June 2017 at 00:37:18 UTC, Jolly James wrote:
>>> Unfortunately, the public DUB package requires to be linked with the libs from pkgBASE/lib. What do I have to add to pkgBASE's dub.json?
>>
>> Side-note: the lib/ should not be moved for portability reasons if this is possible
>
>
>
> My bad solution:
>
>
> "lflags": [
> "-Llib\\"
> ],
>
>
>
> but this requires the lib folder to be part of pkgAPP, not pkgBASE where I would like to have it. Does anyone have an idea?
Replace the lflags directive with this in the pkgBase dub.json:
"libs": [
"$PACKAGE_DIR/libs/foo"
]
|
Copyright © 1999-2021 by the D Language Foundation