2012/4/26 Carnë Draug <carandraug+...@gmail.com>: > On 26 April 2012 13:00, Mike Miller <mtmil...@ieee.org> wrote: >> I've noticed a fair number of Makefiles that call mkoctfile instead of >> the $(MKOCTFILE) variable, this will not work as intended if compiling >> against an Octave in a non-standard path, right? Is this something >> that should be fixed per-package or across the board? For example, >> I'm working in comm, should I just submit a patch for comm's Makefile >> for now? Thanks. > > So all Makefile should use? > > ifndef MKOCTFILE > MKOCTFILE := mkoctfile -Wall > endif > > Is this correct? I'll guess that almost all packages will need this fix.
Good point. True, I was a bit narrow in scope looking at comm because it has a configure script and already has a MKOCTFILE variable defined, oops :) I think I can patch that one as it is today, problem solved, patch forthcoming later. By the way, the current released communications-1.1.0 doesn't build against octave 3.6.1, is there a plan for a 1.1.1 release? I plan to contribute a few functions within the week. I dug a bit more into the broader case of mkoctfile with respect to all packages. Maybe I'm nitpicking but I think it'd be a good feature for packages to install correctly in the case of multiple versions of Octave co-installed or just one version of Octave installed but in a non-standard path. I can follow up later after some more digging with some ideas/notes if you're interested. -- mike ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
