Hi All,

I’d like some advice. In a previous email, Oeyvind pointed out that the install target on Windows did not function as expected.  I’m also having some issues here and I think the CMake files could be modified to get a better experience.

My current thought is this:

1. Cmake installs executables to PREFIX/bin (currently happens)
2. Cmake installs libcsound and interface files into PREFIX/bin (makes things simpler for runtime linking)  (currently installs to PREFIX/lib)
3. Opcodes could install into PREFIX/opcodes (currently installs into PREFIX/lib/plugins64-6.0)
4. Library dependencies would get copied into the folder where the dependent is installed to (currently does not happen; we do have a list of dependent libraries already for linking, it should be simple to use them for installation. The option to copy dependencies could be a commandline flag for further flexibility.)

The resulting path would look something like:

• csound6
• bin
• opcodes

This could be used for easy packaging into other applications, or simplify the installer.  (In my case, I want to simple way to build and use Csound on my computer without having to create and run an installer).

I think the current installer script uses the artifacts from the build step and does not use the install target. If so, any changes I would introduce should not affect the existing installer script.

Thoughts?

Thanks!

steven

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

You snould be able to build and run Csound 6 on your Windows computer without installing it. You just need to make sure that all the shared libraries loaded by Csound at run time are in the PATH, and that you have set OPCODE6DIR64 to your Csound 6 build directory. I used to do this all the time. Since I started using a prebuilt PortAudio library it doesn't work, but it probably could be gotten to work again.

You are correct that the current Windows installer script uses the artifacts from the build step. The installer script puts opcodes in the same "bin" directory as the Csound executables proper.

Would the install target handle dependencies such as libsndfile and portaudio? If so, then it might be better if the installer script did use the install target. The installer script could the mostly just zip up the install target.

Best,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Fri, Dec 27, 2013 at 11:27 AM, <stevenyi@gmail.com> wrote:

Hi All,

I’d like some advice. In a previous email, Oeyvind pointed out that the install target on Windows did not function as expected.  I’m also having some issues here and I think the CMake files could be modified to get a better experience.

My current thought is this:

1. Cmake installs executables to PREFIX/bin (currently happens)
2. Cmake installs libcsound and interface files into PREFIX/bin (makes things simpler for runtime linking)  (currently installs to PREFIX/lib)
3. Opcodes could install into PREFIX/opcodes (currently installs into PREFIX/lib/plugins64-6.0)
4. Library dependencies would get copied into the folder where the dependent is installed to (currently does not happen; we do have a list of dependent libraries already for linking, it should be simple to use them for installation. The option to copy dependencies could be a commandline flag for further flexibility.)

The resulting path would look something like:

• csound6
• bin
• opcodes

This could be used for easy packaging into other applications, or simplify the installer.  (In my case, I want to simple way to build and use Csound on my computer without having to create and run an installer).

I think the current installer script uses the artifacts from the build step and does not use the install target. If so, any changes I would introduce should not affect the existing installer script.

Thoughts?

Thanks!

steven

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel