[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Compiling octave-workshop
From: |
John W. Eaton |
Subject: |
Re: Compiling octave-workshop |
Date: |
Wed, 1 Mar 2006 13:41:15 -0500 |
On 1-Mar-2006, Sebastien Loisel wrote:
| What do you suggest I do instead of these eight commands? I need an
| all-encompassing link line, and an all-encompassing compile line, especially
| containing all the -lfoo I need. One thing I'm thinking of doing is to
| compile a dummy file with mkoctfile with -v and then parse the output to
| figure out the g++ options.
Why not just use "mkoctfile -c" as the compiler? You might also be
able to use mkoctfile --link-stand-alone to perform the final linking
step.
jwe
- Re: Compiling octave-workshop, Sebastien Loisel, 2006/03/01
- Re: Compiling octave-workshop, John W. Eaton, 2006/03/01
- Re: Compiling octave-workshop, Quentin Spencer, 2006/03/01
- Re: Compiling octave-workshop, Sebastien Loisel, 2006/03/01
- Re: Compiling octave-workshop,
John W. Eaton <=
- Re: Compiling octave-workshop, Sebastien Loisel, 2006/03/01
- Re: Compiling octave-workshop, John W. Eaton, 2006/03/01
- Re: Compiling octave-workshop, Sebastien Loisel, 2006/03/01
- Re: Compiling octave-workshop, John W. Eaton, 2006/03/01
- Re: Compiling octave-workshop, Sebastien Loisel, 2006/03/01