github-starred/libxlsxwriter
2
0
Fork 0
mirror of https://github.com/jmcnamara/libxlsxwriter.git synced 2026-05-15 14:15:54 -06:00
Code Issues 16 Projects Packages Wiki Activity Actions

[GH-ISSUE #369] Add SPM Support #292

New issue
Closed
opened 2026-05-05 12:06:40 -06:00 by gitea-mirror · 8 comments
gitea-mirror commented 2026-05-05 12:06:40 -06:00
Owner
Copy link

Originally created by @mariohahn on GitHub (Apr 25, 2022).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/369

Originally assigned to: @jmcnamara on GitHub.

In addition to Cocopods it would be great to also support Swift Package Manager.

Thx for the lib. 🎸

https://github.com/jmcnamara/libxlsxwriter/issues/325

Originally created by @mariohahn on GitHub (Apr 25, 2022). Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/369 Originally assigned to: @jmcnamara on GitHub. In addition to Cocopods it would be great to also support Swift Package Manager. Thx for the lib. 🎸 https://github.com/jmcnamara/libxlsxwriter/issues/325
gitea-mirror 2026-05-05 12:06:40 -06:00
gitea-mirror commented 2026-05-05 12:06:46 -06:00
Author
Owner
Copy link

@jmcnamara commented on GitHub (Apr 25, 2022):

There is already a Swift package for libxlsxwriter: https://swiftpackageregistry.com/damuellen/xlsxwriter.swift

<!-- gh-comment-id:1108883574 --> @jmcnamara commented on GitHub (Apr 25, 2022): There is already a Swift package for libxlsxwriter: https://swiftpackageregistry.com/damuellen/xlsxwriter.swift
gitea-mirror commented 2026-05-05 12:06:47 -06:00
Author
Owner
Copy link

@jmcnamara commented on GitHub (Apr 28, 2022):

@mariohahn Is the linked package sufficient. Can this request be closed?

<!-- gh-comment-id:1111792325 --> @jmcnamara commented on GitHub (Apr 28, 2022): @mariohahn Is the linked package sufficient. Can this request be closed?
gitea-mirror commented 2026-05-05 12:06:49 -06:00
Author
Owner
Copy link

@jmcnamara commented on GitHub (Apr 29, 2022):

Closing.

<!-- gh-comment-id:1113027516 --> @jmcnamara commented on GitHub (Apr 29, 2022): Closing.
gitea-mirror commented 2026-05-05 12:06:50 -06:00
Author
Owner
Copy link

@willm132 commented on GitHub (May 12, 2022):

There is already a Swift package for libxlsxwriter: https://swiftpackageregistry.com/damuellen/xlsxwriter.swift

This does not work or compile so that is not sufficient

<!-- gh-comment-id:1124965771 --> @willm132 commented on GitHub (May 12, 2022): > There is already a Swift package for libxlsxwriter: https://swiftpackageregistry.com/damuellen/xlsxwriter.swift This does not work or compile so that is not sufficient
gitea-mirror commented 2026-05-05 12:06:52 -06:00
Author
Owner
Copy link

@jmcnamara commented on GitHub (May 12, 2022):

@willm132 You need to take that up with the Swift Package maintainer. There isn't anything I can do about it.

<!-- gh-comment-id:1125481362 --> @jmcnamara commented on GitHub (May 12, 2022): @willm132 You need to take that up with the Swift Package maintainer. There isn't anything I can do about it.
gitea-mirror commented 2026-05-05 12:06:55 -06:00
Author
Owner
Copy link

@orchetect commented on GitHub (May 28, 2024):

Just FYI: the release tags for the repo are not compatible with SPM. Which greatly limits the ability to use the library as a Swift package. SPM looks for SemVer tags (ie: "1.1.7"), so it won't understand "RELEASE_1.1.7"

This is causing showstopping issues in an open-source project I'm working on. The only current solution is to fork the repo and re-tag which is not really sustainable.

If the library is used as a dependency in an app then it may be possible to just use main branch or a specific tag. But It cannot be used as a dependency within another Swift package because Xcode will not compile, citing an unstable dependency.

The easiest resolution would be to tag the repo as SemVer instead of "RELEASE_x.x.x". If that's not viable, then tagging the repo twice would work fine, one tag as SemVer and the other as "RELEASE_x.x.x".

<!-- gh-comment-id:2136214276 --> @orchetect commented on GitHub (May 28, 2024): Just FYI: the release tags for the repo are not compatible with SPM. Which greatly limits the ability to use the library as a Swift package. SPM looks for SemVer tags (ie: "1.1.7"), so it won't understand "RELEASE_1.1.7" This is causing showstopping issues in an open-source project I'm working on. The only current solution is to fork the repo and re-tag which is not really sustainable. If the library is used as a dependency in an app then it may be possible to just use main branch or a specific tag. But It cannot be used as a dependency within another Swift package because Xcode will not compile, citing an unstable dependency. The easiest resolution would be to tag the repo as SemVer instead of "RELEASE_x.x.x". If that's not viable, then tagging the repo twice would work fine, one tag as SemVer and the other as "RELEASE_x.x.x".
gitea-mirror commented 2026-05-05 12:06:56 -06:00
Author
Owner
Copy link

@jmcnamara commented on GitHub (May 29, 2024):

SPM looks for SemVer tags (ie: "1.1.7"), so it won't understand "RELEASE_1.1.7"

Does it have to be "1.1.7" or can it be "v1.1.7".

<!-- gh-comment-id:2136325377 --> @jmcnamara commented on GitHub (May 29, 2024): > SPM looks for SemVer tags (ie: "1.1.7"), so it won't understand "RELEASE_1.1.7" Does it have to be "1.1.7" or can it be "v1.1.7".
gitea-mirror commented 2026-05-05 12:06:57 -06:00
Author
Owner
Copy link

@orchetect commented on GitHub (May 29, 2024):

Does it have to be "1.1.7" or can it be "v1.1.7".

Ideally "1.1.7", but "v1.1.7" is also recognized.

<!-- gh-comment-id:2136338098 --> @orchetect commented on GitHub (May 29, 2024): > Does it have to be "1.1.7" or can it be "v1.1.7". Ideally "1.1.7", but "v1.1.7" is also recognized.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
coverity
cmake-improvements
cmake_pkgconfig_fix
ctest
button
tables
autofilter
dtoa
iwyu
openssl
gentoo
gh310
condition_format
rich_string_html
header_footer_images
custom_data_labels
object_position
gh265
constant_mode_comments2
constant_mode_comments
vml
md5
vcpkg
hyperlinks
api_refactor
win_fopen
gh203
rich_strings
chartsheet
in_mem_image
gh192
revert-162-master
data_validation
meson
charts
scan_build
utf8_strlen
tmpfileplus
custom_properties
insert_image
default_row
control_chars
worksheet_protect
dev
red_black
panes
mkstemp
defined_names
optimise
wip
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.9
v1.1.8
RELEASE_1.1.7
RELEASE_1.1.6
RELEASE_1.1.5
RELEASE_1.1.4
RELEASE_1.1.3
RELEASE_1.1.2
RELEASE_1.1.1
RELEASE_1.1.0
RELEASE_1.0.9
RELEASE_1.0.8
RELEASE_1.0.7
RELEASE_1.0.6
RELEASE_1.0.5
RELEASE_1.0.4
RELEASE_1.0.3
RELEASE_1.0.2
RELEASE_1.0.1
RELEASE_1.0.0
RELEASE_0.9.9
RELEASE_0.9.8
RELEASE_0.9.7
RELEASE_0.9.6
RELEASE_0.9.5
RELEASE_0.9.4
RELEASE_0.9.3
RELEASE_0.9.2
RELEASE_0.9.1
RELEASE_0.9.0
RELEASE_0.8.9
RELEASE_0.8.8
RELEASE_0.8.7
RELEASE_0.8.6
RELEASE_0.8.5
RELEASE_0.8.4
RELEASE_0.8.3
RELEASE_0.8.2
RELEASE_0.8.1
RELEASE_0.8.0
RELEASE_0.7.9
RELEASE_0.7.8
RELEASE_0.7.7
RELEASE_0.7.6
RELEASE_0.7.5
RELEASE_0.7.4
RELEASE_0.7.3
RELEASE_0.7.2
RELEASE_0.7.1
RELEASE_0.7.0
RELEASE_0.6.9
RELEASE_0.6.8
RELEASE_0.6.7
RELEASE_0.6.6
RELEASE_0.6.5
RELEASE_0.6.4
RELEASE_0.6.3
RELEASE_0.6.2
RELEASE_0.6.1
RELEASE_0.6.0
RELEASE_0.5.9
RELEASE_0.5.8
RELEASE_0.5.7
RELEASE_0.5.6
RELEASE_0.5.5
RELEASE_0.5.4
RELEASE_0.5.3
RELEASE_0.5.2
RELEASE_0.5.1
RELEASE_0.5.0
RELEASE_0.4.9
RELEASE_0.4.8
RELEASE_0.4.7
RELEASE_0.4.6
RELEASE_0.4.5
RELEASE_0.4.4
RELEASE_0.4.3
RELEASE_0.4.2
RELEASE_0.4.1
RELEASE_0.4.0
RELEASE_0.3.9
RELEASE_0.3.8
RELEASE_0.3.7
RELEASE_0.3.6
RELEASE_0.3.5
RELEASE_0.3.4
RELEASE_0.3.3
RELEASE_0.3.2
RELEASE_0.3.1
RELEASE_0.3.0
RELEASE_0.2.9
RELEASE_0.2.8
RELEASE_0.2.7
RELEASE_0.2.6
RELEASE_0.2.5
RELEASE_0.2.4
RELEASE_0.2.3
RELEASE_0.2.2
RELEASE_0.2.1
RELEASE_0.2.0
RELEASE_0.1.9
RELEASE_0.1.8
RELEASE_0.1.7
RELEASE_0.1.6
RELEASE_0.1.5
RELEASE_0.1.4
RELEASE_0.1.3
RELEASE_0.1.2
RELEASE_0.1.1
RELEASE_0.1.0
RELEASE_0.0.9
RELEASE_0.0.8
RELEASE_0.0.7
RELEASE_0.0.6
RELEASE_0.0.5
RELEASE_0.0.4
RELEASE_0.0.3
RELEASE_0.0.2
RELEASE_0.0.1
Labels
Clear labels   
awaiting user feedback

   
bug

   
cmake

   
cmake

   
docs

   
feature request

   
in progress

   
long term

   
medium term

   
medium term

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
ready to close

   
short term

   
under investigation

   
wontfix
No labels
awaiting user feedback
bug
cmake
cmake
docs
feature request
in progress
long term
medium term
medium term
pull-request
question
question
ready to close
short term
under investigation
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/libxlsxwriter#292
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?