ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I was having an issue with namespaces and compiling a Lex-generated lexer, so I though that the simplest solution would simply be to wrap namespace constructs around Lex's output before compiling (I know, it's not really an elegant solution, but I couldn't think of anything much better).
Oops, my bad. I guess I miscounted them when I first looked.
Does your sed command work as specified, but independently of make? Does the input file exist? Non-empty? Where its supposed to be when make runs?
Oops, my bad. I guess I miscounted them when I first looked.
Does your sed command work as specified, but independently of make? Does the input file exist? Non-empty? Where its supposed to be when make runs?
--- rod.
That's kind of irrelavent becasue when you look at the error messages, it's /bin/sh, not sed, throwing the error.
I think that the biggest problem is that I don't understand how the command is executed by CMake. Is it passed unmodified to bash? Does CMake interpret certain quotes and escape characters?
I thought that CMake interprets them becasue Kate doesn't highlight single quotes, and even if I do try them, CMake interprets the '#' characters as the start of a comment. And then bash says that there's an unmatched single quote.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.