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

Quotes removed in setup_command #261

Closed
ilfreddy opened this issue Feb 11, 2020 · 11 comments
Closed

Quotes removed in setup_command #261

ilfreddy opened this issue Feb 11, 2020 · 11 comments

Comments

@ilfreddy
Copy link
Contributor

ilfreddy commented Feb 11, 2020

The setup command line of each build is stored in setup_command for future reference. However, when more than one option is passed to cmake via the --cmake_options flag, the sting is stored without hyphens --cmake_options=-Doption_a -Doption_b. The right command line should contain --cmake_options='-Doption_a -Doption_b'.
I guess it has to do with the handling of such a string by python.

@robertodr robertodr changed the title Hyphens removed in setup_command Quotes removed in setup_command Feb 11, 2020
@robertodr
Copy link
Contributor

I think we hit this problem 2-3 years ago with @bast and the conclusion was that it's actually the shell that handles quotes, not Python. So it's next to impossible to do what you ask in a consistent manner.

@ilfreddy
Copy link
Contributor Author

ilfreddy commented Feb 11, 2020

Can we put a "reminder" in a separate line?

Something like:

./setup option option option
WARNING: remember to add missing quotes if necessary

It would spare us some time, considering that we will eventually forget that, given that it happens with the frequency of a leap year.

@bast
Copy link
Member

bast commented Feb 11, 2020

This is where we already wrestled with it: dev-cafe/autocmake#169

@ilfreddy
Copy link
Contributor Author

ilfreddy commented Apr 6, 2020

What I suggest as a "patch" is simply to append the WARNING line in the file setup_command. This should be doable, or?

@bast
Copy link
Member

bast commented Apr 7, 2020

Warning is definitely doable. I will again look at this issue.

@ilfreddy
Copy link
Contributor Author

ilfreddy commented Apr 7, 2020

But don't work in shifts for it, OK? ;-)

@robertodr
Copy link
Contributor

But don't work in shifts for it, OK? ;-)

We have a team on it.

@bast
Copy link
Member

bast commented Apr 7, 2020

I looked at it again and here are my findings: dev-cafe/autocmake#169 (comment). So there might be a solution.

@bast
Copy link
Member

bast commented Apr 7, 2020

There is a solution: dev-cafe/autocmake#264 - once this is in, it will require that you regenerate setup.

@robertodr
Copy link
Contributor

@ilfreddy Radovan's fix in dev-cafe/autocmake#264 has now been merged. You should regenerate
the setup script:

cd cmake
python update.py --self
python update.py ..

and try again.

@stigrj
Copy link
Contributor

stigrj commented Apr 8, 2020

Fixed by #291

@stigrj stigrj closed this as completed Apr 8, 2020
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

4 participants