You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got a decent cmake file for building plugins... see my fork of ZMQInterface. Nevermind the rest of what I've done to that plugin...
Need to put some attribution at the top of the file, but other than that I'd be happy to adapt it for this plugin. You use ccmake to tell it where open ephys is, and it selects the correct install location for the platform (on macs, this is under ~/Application\ Support/open-ephys/PlugIns, not in the open ephys build path).
It can make xcode projects, make files, and project files for whatever IDE's cmake supports (though I've only tested those first two).
It can also generate customized environment.xcconfig files, so should take care of that pesky python path / version issue in the xcode build process.
Let me know if you'd like me to put something together!
I haven't looked at @beOn's fork, but it sounds like it might be possible to incorporate the logic for setting the Python path into a CMake config file based on the template, and use that to replace the various python path setting mechanisms for each platform (e.g. build-linux.sh for Linux and PythonEnv.props for Windows).
I've got it up and running on the mac build, and it's pretty super.
Working on the linux build... and I could use a volunteer to help testing
out the windows build process.
On Wed, May 29, 2019 at 4:33 AM Francesco Battaglia < ***@***.***> wrote:
Always tried to avoid cmake, but if somebody understands it well enough,
and it can deal with the paths stuff etc, then that's great
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAL4RH5YZLWYQJVNP7XRT3PXZEWXANCNFSM4HCJT6FQ>
.
Activity
Claybarn commentedon Mar 30, 2019
Definitely! The python path issue is a real pain. Would be awesome to get around that. Be sure to develop with the “event_reciever” branch.
ethanbb commentedon May 28, 2019
To add on, there is now this standard template for using CMake for Open Ephys plugins: https://github.com/open-ephys-plugins/OEPlugin
I haven't looked at @beOn's fork, but it sounds like it might be possible to incorporate the logic for setting the Python path into a CMake config file based on the template, and use that to replace the various python path setting mechanisms for each platform (e.g.
build-linux.shfor Linux andPythonEnv.propsfor Windows).fpbattaglia commentedon May 29, 2019
Always tried to avoid cmake, but if somebody understands it well enough, and it can deal with the paths stuff etc, then that's great
beOn commentedon May 29, 2019
fpbattaglia commentedon May 31, 2019
just created a "cmake_build" branch. Do you want to send a PR onto that? Then we can all take a look...
beOn commentedon May 31, 2019
Sure thing. Will have to hit this tonight or over the weekend... updating my branch from master just now created a bit of a mess.
beOn commentedon Jun 14, 2019
Submitted. Some quick notes I'll need to edit, extend and add to the readme:
readme notes