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

File "private/soci-trivial-blob-backend.h" missing #1153

Open
Spixmaster opened this issue Jun 7, 2024 · 5 comments · May be fixed by #1165
Open

File "private/soci-trivial-blob-backend.h" missing #1153

Spixmaster opened this issue Jun 7, 2024 · 5 comments · May be fixed by #1165

Comments

@Spixmaster
Copy link
Contributor

@Krzmbrzl, the commit #992 includes #include <private/soci-trivial-blob-backend.h> which is not present when installed with CMake.

@Krzmbrzl
Copy link
Contributor

Krzmbrzl commented Jun 7, 2024

See my revamp cmake PR. I think there this should be fixed

@Spixmaster
Copy link
Contributor Author

#1118 for reference.

@vadz
Copy link
Member

vadz commented Jun 8, 2024

Private headers are not supposed to be installed, so if this header is used by the public headers, it can't be private.

I.e. it's not (just) a build system problem, it's a problem with the header name/path.

@Spixmaster
Copy link
Contributor Author

Spixmaster commented Jun 8, 2024

The header is used two times, here and here.

Krzmbrzl added a commit to Krzmbrzl/soci that referenced this issue Aug 31, 2024
Since private headers are (and also should not be) installed, this
makes it impossible to compile SOCI as an installed package.

Fixes SOCI#1153
Krzmbrzl added a commit to Krzmbrzl/soci that referenced this issue Aug 31, 2024
Since private headers are (and also should not be) installed, this
makes it impossible to compile SOCI as an installed package.

Fixes SOCI#1153
@Krzmbrzl Krzmbrzl linked a pull request Aug 31, 2024 that will close this issue
@Krzmbrzl
Copy link
Contributor

I had another look at this and am now in line with what @vadz said. That is, I misused private headers. Consequently, this is fixed in #1165

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

Successfully merging a pull request may close this issue.

3 participants