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

c3c --print-env feature request #1832

Open
alexveden opened this issue Jan 13, 2025 · 2 comments
Open

c3c --print-env feature request #1832

alexveden opened this issue Jan 13, 2025 · 2 comments
Labels
Enhancement Request New feature or request
Milestone

Comments

@alexveden
Copy link
Contributor

For tooling prospective, it would be nice to have a c3c option that prints its build environment (maybe in json format):

  1. c3c version
  2. standard lib path used for project (must have for LSPs)
  3. c3c path
  4. build output path
  5. environment flags state which is used by attributes, i.e. $if(env::LIBC)
  6. Anything else what could be altered by project.json maybe?

This is a low priority request, though.

@lerno lerno added the Enhancement Request New feature or request label Jan 14, 2025
@lerno lerno added this to the 0.6.7 milestone Jan 14, 2025
@lerno
Copy link
Collaborator

lerno commented Jan 14, 2025

Can you show a mockup of what you want?

@alexveden
Copy link
Contributor Author

I think simple JSON output would be sufficient:

{
"c3c": {
  "version": "0.6.5",
  "stdlib": "/some/path",
  "c3c_exe": "/another/path/c3c.exe",
},
{
"project": {
  "path": "/current/project/path",
  "target": "current target",
},
{
"environment": {
  "system_path": "$PATH",
  "os": "win32",
  "variables": {
   // text should match to @if() attribute text in c3 code
    "env::POSIX": false,
     "env::win32": true,
     "LIBC": true,
     "SOME_USER_DEF": true, // in project.json if it's allowed
}

}

}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants