You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On debian, QT_PATH should be "/usr/include/x86_64-linux-gnu/qt5" and on arch linux, QT_PATH is "/usr/include/qt". It's unfortunate that the WORKSPACE file must be modified depending on which system you're trying to build your app on. It would be nice to have bazel auto-detect this somehow.
The text was updated successfully, but these errors were encountered:
@justbuchanan In case you are interested, I started working on a way to autodetect the system limdor#6, next step will be to read it from an environment variable limdor#13
That looks great! I have a project that I develop on a debian computer and an acrh linux computer, so being able to set QT_DIR and have it just work would be awesome (previously I was editing WORKSPACE). Especially nice that the repository_ctx approach easily adapts to use on windows.
In order to use bazel_rules_qt in a bazel project, this must be added to the WORKSPACE fiile:
On debian, QT_PATH should be "/usr/include/x86_64-linux-gnu/qt5" and on arch linux, QT_PATH is "/usr/include/qt". It's unfortunate that the WORKSPACE file must be modified depending on which system you're trying to build your app on. It would be nice to have bazel auto-detect this somehow.
The text was updated successfully, but these errors were encountered: