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

The gojsonnet lib instead of the C++ libjsonnet should be made default #342

Open
brettviren opened this issue Sep 19, 2024 · 2 comments
Open

Comments

@brettviren
Copy link
Member

The Go version of the Jsonnet library is far faster than the C++ version and I believe everyone (?) uses it. This requires the user to give an option when configuring the build.

This should be switched so that gojsonnet is the default and anyone stuck with the C++ libjsonnet external may specify an option.

This issue is meant to stew for a bit to see if this switch would cause major breakage.

To effect it, the 'Jsonnet' libs= entry in waft/wcb.py needs editing.

@HaiwangYu
Copy link
Member

Hi @brettviren ,

Currently the 'Jsonnet' entry in waft/wcb.py shows

('Jsonnet',  dict(incs=["libjsonnet.h"], libs=['jsonnet'])),

At configure time, I am using:

--with-jsonnet-include="$GOJSONNET_FQ_DIR/include" \  
--with-jsonnet-lib="$GOJSONNET_FQ_DIR/lib" \    

So what will be the changes in your proposal?

@brettviren
Copy link
Member Author

The change involves adding "go" to the libs name:

 ('Jsonnet',  dict(incs=["libjsonnet.h"], libs=['gojsonnet'])),

A user will still supply --with-jsonnet-{lib,include} (assuming their Jsonnet is not found automatically) but they would no longer need to supply --with-jsonnet-libs=gojsonnet.

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

No branches or pull requests

2 participants