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

Have no note to introduce how to build and install libcJSON.so. #19

Closed
ryanleiwang opened this issue Jul 18, 2016 · 4 comments
Closed

Have no note to introduce how to build and install libcJSON.so. #19

ryanleiwang opened this issue Jul 18, 2016 · 4 comments

Comments

@ryanleiwang
Copy link

Have no note to introduce how to build and install libcJSON.so in README.
Most open source project depending on cjson by shared library libcJSON.so, so that I think we need to add note to introduce how to build and install libcJSON.so.
@DaveGamble
Copy link
Owner

Um... what's libcJSON.so?

@ryanleiwang
Copy link
Author

File libcJSON.so is a shared library, it is liked lib*.dll in MS-Windows system.
In the README file, introduce one usage of cJSON(gcc cJSON.c test.c -o test -lm ). But I think that it is not better way in linux.

If you use cJSON source code in a lot of your projects, and they are installed in a same OS.
Upgrade and update source code of cJSON is a big trouble.If all your projects only depend on one libcjson.so, update cjson will become a easy job.

@DaveGamble
Copy link
Owner

DaveGamble commented Sep 11, 2016 •
edited
Loading

But... there's no process for standardising the API, there's no standardisation of the name even... ?
How does this make sense?
cJSON is a code-level library that you link in. If I change something in the code and you recompile the .so, you could VERY easily break working projects.
I think this is a bad idea; this makes it far too easy to break things by accident.

@FSMaxB
Copy link
Collaborator

FSMaxB commented Nov 7, 2016

The 1.0.0 release will contain instructions on building and installing cJSON.

@cjsheng cjsheng mentioned this issue Dec 31, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DaveGamble @FSMaxB @ryanleiwang