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.

Sign up for GitHub

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

Jump to bottom

Refactor project code so there is a clearer client/library distinction #40

Open
grunt-lucas opened this issue Apr 6, 2024 · 0 comments
Open

Refactor project code so there is a clearer client/library distinction #40

grunt-lucas opened this issue Apr 6, 2024 · 0 comments
Assignees
@grunt-lucas
Labels
refactoring Code cleanup that doesn't significantly alter functionality
Milestone
Porytiles 2.x

Comments

@grunt-lucas
Copy link
Owner

It would be nice if we could publish some kind of libporytiles, maybe in the form of a .a/.so/.dylib, as well as a header-only library. That way e.g. Porymap could vendor the header-only lib for integration, or other developers could use the library for their own purposes, etc.
@grunt-lucas grunt-lucas added the meta Repository housekeeping label Apr 6, 2024
@grunt-lucas grunt-lucas self-assigned this Apr 6, 2024
@grunt-lucas grunt-lucas added refactoring Code cleanup that doesn't significantly alter functionality and removed meta Repository housekeeping labels Apr 6, 2024
@grunt-lucas grunt-lucas mentioned this issue Jul 19, 2024
Closed
@grunt-lucas grunt-lucas added this to the 2.0.0 Refactor Effort milestone Sep 14, 2024
@grunt-lucas grunt-lucas mentioned this issue Sep 15, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@grunt-lucas grunt-lucas

Labels
refactoring Code cleanup that doesn't significantly alter functionality
Projects
None yet
Milestone
Porytiles 2.x
Development

No branches or pull requests
1 participant
@grunt-lucas