from IDE to (c)make file
Posted: Thu Jan 22, 2015 9:59 am
Hi Eran,
I have a CL project I'd like to deploy on github. I want to add cmd-line build instructions (with Make or CMake, either is fine) so it doesn't require CL, while keeping it CL-friendly since it's all I use.
What procedure do you suggest to create and maintain such a project?
I.e. is there a way to "extract" a generic make/cmake file (or part thereof) from CL's project settings? F.ex. is there a way to post-process the "*.mk" file that CL produces, say with a regex parser?
If that doesn't make sense, what is the recommended way to use CL in such a scenario where we want to 3rd parties to be able to build with the cmd-line while (off-handedly
) suggesting they should use CL ?
The dependencies are:
$WXCONF_PATH for wxWidgets
$PORTAUDIO for https://subversion.assembla.com/svn/por ... portaudio/
$RTMIDI for https://github.com/thestk/rtmidi
those are currently defined as CL env vars (either directly or pre-processed in project env vars) and I presume should become something like -DXXX_DEP_VAR1.
My project is a DJ tool "soft-router" that samples audio from CDJs reading CD-Rs with a custom control wave burned onto them, it converts the analog signal, then writes custom MIDI messages (sysex) to a software MIDI interface that a program like Mixxx can read from.
It doesn't require root auth so I'd rather keep the deps flexible too, i.e. not require system-wide install. It's theoretically Windows-friendly but I really only care about Linux.
thx a lot!
-- p
I have a CL project I'd like to deploy on github. I want to add cmd-line build instructions (with Make or CMake, either is fine) so it doesn't require CL, while keeping it CL-friendly since it's all I use.
What procedure do you suggest to create and maintain such a project?
I.e. is there a way to "extract" a generic make/cmake file (or part thereof) from CL's project settings? F.ex. is there a way to post-process the "*.mk" file that CL produces, say with a regex parser?
If that doesn't make sense, what is the recommended way to use CL in such a scenario where we want to 3rd parties to be able to build with the cmd-line while (off-handedly
) suggesting they should use CL ?The dependencies are:
$WXCONF_PATH for wxWidgets
$PORTAUDIO for https://subversion.assembla.com/svn/por ... portaudio/
$RTMIDI for https://github.com/thestk/rtmidi
those are currently defined as CL env vars (either directly or pre-processed in project env vars) and I presume should become something like -DXXX_DEP_VAR1.
My project is a DJ tool "soft-router" that samples audio from CDJs reading CD-Rs with a custom control wave burned onto them, it converts the analog signal, then writes custom MIDI messages (sysex) to a software MIDI interface that a program like Mixxx can read from.
It doesn't require root auth so I'd rather keep the deps flexible too, i.e. not require system-wide install. It's theoretically Windows-friendly but I really only care about Linux.
thx a lot!
-- p
