Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building against system's versions of tarball dependencies #74

Open
OPNA2608 opened this issue Mar 29, 2021 · 0 comments
Open

Building against system's versions of tarball dependencies #74

OPNA2608 opened this issue Mar 29, 2021 · 0 comments

Comments

@OPNA2608
Copy link

I would prefer to build this repository devendored, supplying my system's versions of Boost, cc65, RtMidi etc instead of downloading the nesicide-deps tarball. Would it be possible to add qmake config options or some detection mechanism to use system-installed versions of them instead? Getting rid of the deps tarball altogether would be even better, but baby steps.

Example from another project:

https://github.com/rerrahkr/BambooTracker/blob/fdb048e67c7fdc18b709b55fee5300cf90a611fb/BambooTracker/BambooTracker.pro#L485-L510
https://github.com/rerrahkr/BambooTracker/blob/fdb048e67c7fdc18b709b55fee5300cf90a611fb/submodules/RtMidi/RtMidi.pro#L3-L10

If CONFIG+=system_rtmidi is passed to qmake, it will use pkg-config to find the system's RtMidi installation and error out of it's missing. If it isn't passed, it's expected that the user cloned the repo with --recurse-submodules to get the source code from the https://github.com/thestk/rtmidi/ repository and RtMidi is built from source & linked statically into the final binary.

@OPNA2608 OPNA2608 changed the title Using against system's versions of tarball dependencies Building against system's versions of tarball dependencies Mar 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant