[Cs-dev] hard coded path in makefile? (win)
Date | 2014-01-09 19:56 |
From | Oeyvind Brandtsegg |
Subject | [Cs-dev] hard coded path in makefile? (win) |
When I build Csound, it seems I need to have an excisting version of Csound in the path 'C:/Program Files (x86)/Csound/' as I get this error if not: mingw32-make[2]: *** No rule to make target 'C:/Program Files (x86)/Csound/bin/libsndfile-1.dll', needed by 'csound64.dll'. Stop. Now, I am no expert at the build system, but I'm quite sure I did not set this path anywhere. I do have my csound 6 installation in 'C:/Program Files (x86)/Csound6/ and also a csound 5 installation similarly in 'C:/Program Files (x86)/Csound5/ The current windows installer also installs to 'C:/Program Files (x86)/Csound6/, I also have my system path variables set up to point to the csound5 and csound6 installation paths as indicated above. Every time I build I must rename my csound6 folder to csound, then build, install, rename it again to csound6. No big deal, but after a few build cycles today, I figured I'd try to hunt down this one. Where could the reference to this path be located? -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://flyndresang.no/ http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://soundcloud.com/t-emp ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2014-01-09 20:18 |
From | Michael Gogins |
Subject | Re: [Cs-dev] hard coded path in makefile? (win) |
Attachments | None None |
Run cmake-gui and configure it and examine the paths for dependent libraries. The CMake files probably got committed with an inappropriate path by me. Just change the paths to what you actually have. In general as you probably know you do not want to use the makefile without configuring it first. cmake or cmake-gui are tools for configuring the makefiles. Hope this helps, Mike
----------------------------------------------------- Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Thu, Jan 9, 2014 at 2:56 PM, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: When I build Csound, it seems I need to have an excisting version of |
Date | 2014-01-09 20:22 |
From | Steven Yi |
Subject | Re: [Cs-dev] hard coded path in makefile? (win) |
It may also be the case that that was where the library was first found and the value was cached. Once cached, it won't look for that value again. You can check the value in CMakeCache.txt in the build folder, or use cmake-gui. Either way, you can hand-edit the value and it should pick up from the new location. On Thu, Jan 9, 2014 at 3:18 PM, Michael Gogins |
Date | 2014-01-09 20:35 |
From | Michael Gogins |
Subject | Re: [Cs-dev] hard coded path in makefile? (win) |
Attachments | None None |
Yes, what Steven is talking about has happened to me. Very annoying, but easy to fix. Regards, Mike ----------------------------------------------------- Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Thu, Jan 9, 2014 at 3:22 PM, Steven Yi <stevenyi@gmail.com> wrote: It may also be the case that that was where the library was first |
Date | 2014-01-09 21:05 |
From | Oeyvind Brandtsegg |
Subject | Re: [Cs-dev] hard coded path in makefile? (win) |
aha, excellent, that was it. I had used cmake-gui, struggled a bit with it at first, and in the end I just kept hitting "configure" until all the reds were gone, then "generate" and since it seemed to work I did not think any more about it. I still run cmake-gui after each pull, is that not necessary? 2014/1/9 Michael Gogins |
Date | 2014-01-09 21:45 |
From | Michael Gogins |
Subject | Re: [Cs-dev] hard coded path in makefile? (win) |
Attachments | None None |
That should not be necessary. But if "make" detects a change in CMakeLists.txt or other CMake files, it will automatically run the configure and generate steps again. Regards,
Mike ----------------------------------------------------- Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Thu, Jan 9, 2014 at 4:05 PM, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: aha, excellent, that was it. |