Skip to content

Conversation

@teo-tsirpanis
Copy link
Member

@teo-tsirpanis teo-tsirpanis commented Oct 25, 2023

SC-34269

Since the macOS and Linux release artifacts already contain only dynamic libraries, this should have effect only on Windows (where we bundle tiledb.dll in the maven package either way).

Let's see what CI thinks.

@shortcut-integration
Copy link

@teo-tsirpanis teo-tsirpanis marked this pull request as ready for review October 25, 2023 14:05
@DimitrisStaratzis
Copy link
Contributor

Thank you @teo-tsirpanis. Looks LGTM. I will do some testing tomorrow and approve.

@DimitrisStaratzis
Copy link
Contributor

Playing with CI to test releases. Will revert my changes

@DimitrisStaratzis DimitrisStaratzis merged commit 28b106c into master Oct 26, 2023
@DimitrisStaratzis DimitrisStaratzis deleted the teo/dynamic-link branch October 26, 2023 11:24
KiterLuc pushed a commit to TileDB-Inc/TileDB that referenced this pull request Oct 31, 2023
This PR stops passing `-EnableStaticTileDB` on the Windows release
workflow, which means that the release artifacts will include include
only the dynamic library, like on other platforms. The size of these
artifacts on Windows drops from 175MB [to just
7MB](https://dev.azure.com/TileDB-Inc/CI/_build/results?buildId=35970&view=artifacts&pathAsName=false&type=publishedArtifacts).

Users that want to statically link to TileDB will have to build it
themselves. TileDB-Java used to do that until
TileDB-Inc/TileDB-Java#314, and according to [a
search](https://github.com/search?q=TileDB%3A%3Atiledb_static++NOT+is%3Aarchived+NOT+is%3Afork&type=code)
of the `TileDB::tiledb_static` string on public non-archived and
non-forked repositories, none of these uses would be broken.

> [!NOTE]
> TileDB-R links statically on Windows as well but it does not use these
artifacts so it will not be affected.

---
TYPE: BREAKING_BEHAVIOR
DESC: The Windows release artifacts no longer include static libraries.
github-actions bot pushed a commit to TileDB-Inc/TileDB that referenced this pull request Nov 1, 2023
This PR stops passing `-EnableStaticTileDB` on the Windows release
workflow, which means that the release artifacts will include include
only the dynamic library, like on other platforms. The size of these
artifacts on Windows drops from 175MB [to just
7MB](https://dev.azure.com/TileDB-Inc/CI/_build/results?buildId=35970&view=artifacts&pathAsName=false&type=publishedArtifacts).

Users that want to statically link to TileDB will have to build it
themselves. TileDB-Java used to do that until
TileDB-Inc/TileDB-Java#314, and according to [a
search](https://github.com/search?q=TileDB%3A%3Atiledb_static++NOT+is%3Aarchived+NOT+is%3Afork&type=code)
of the `TileDB::tiledb_static` string on public non-archived and
non-forked repositories, none of these uses would be broken.

> [!NOTE]
> TileDB-R links statically on Windows as well but it does not use these
artifacts so it will not be affected.

---
TYPE: BREAKING_BEHAVIOR
DESC: The Windows release artifacts no longer include static libraries.

(cherry picked from commit af3cbf8)
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 this pull request may close these issues.

2 participants