-
Notifications
You must be signed in to change notification settings - Fork 240
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
Add project() to sqlite3_cmakelists.txt #324
Conversation
Signed-off-by: Stephen Brawner <brawner@gmail.com>
You repos file is incorrect I believe:
the url should be provided in form of |
I actually think naming it |
d502f68
to
8c09f7a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like the osrf testing tools are giving the windows CI a hard time. Maybe you can retrigger CI and explicitly skip that package? Should be unrelated to this change here anyway.
install(FILES sqlite3.h sqlite3ext.h DESTINATION include) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't quite see it, but what's the diff here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A newline was added at the end of the file (my editor does this automatically). Let me know if this needs to be changed back
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's all good. I was just wondering as GitHub doesn't really seem to render this change.
Does it make sense to run the windows CI job without cyclone and connext? I think these CI failures are addressed more appropriately at another place and shouldn't really block to move this PR further. |
Building on windows finally passed. Failing test is a known issue (#305) |
Attempting to address issue #323. I'm not sure if this is the correct way of going about this since it's being included from another cmakelists.txt. I'm also open to naming the project whatever you all think is appropriate. I just didn't want to name it sqlite3_vendor (already taken) nor sqlite3 (may conflict with another cmake project?).
Signed-off-by: Stephen Brawner brawner@gmail.com