[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.9.11?
From: |
John W. Eaton |
Subject: |
Re: 2.9.11? |
Date: |
Thu, 19 Apr 2007 13:00:07 -0400 |
On 19-Apr-2007, Michael Goffioul wrote:
| On 4/19/07, Thomas Weber <address@hidden> wrote:
| > Am Donnerstag, 19. April 2007 09:47 schrieb Michael Goffioul:
| > > 2) "configure" script must be called with additional settings, to
correctly
| > > define compiler; the command should looks like:
| >
| > > CC=cc-msvc CXX=cc-msvc AR=ar-msvc RANLIB=ranlib-msvc ./configure
| > > Would it be OK to use octave_config_info('config_opts') to achieve this?
| > > (I mean, is it OK for other platforms?)
| >
| > This is an issue we are facing in Debian as well: how to pass additional
flags
| > to the configure script. Did you hardcode your changes into pkg.m?
|
| For the time being, yes. But I could probably also use:
|
| system(['cd src; ./configure ', octave_config_info('config_opts')]);
|
| although I didn't test it yet. But the point here is that I want to use the
| same flags as those used to compile octave itself. Adding *new* flags
| is something different.
Shouldn't an Octave package use mkoctfile to compile things? Aren't
the compiler options recorded in mkoctfile?
jwe
Re: 2.9.11?, Michael Goffioul, 2007/04/19
- Re: 2.9.11?, Thomas Weber, 2007/04/19
- Re: 2.9.11?, Michael Goffioul, 2007/04/19
- Re: 2.9.11?, Paul Kienzle, 2007/04/19
- Re: 2.9.11?,
John W. Eaton <=
- Re: 2.9.11?, Michael Goffioul, 2007/04/19
- Re: 2.9.11?, John W. Eaton, 2007/04/25
- Re: 2.9.11?, Michael Goffioul, 2007/04/25
Re: 2.9.11?, John W. Eaton, 2007/04/19
Re: 2.9.11?, Thomas Weber, 2007/04/19
Re: 2.9.11?, John W. Eaton, 2007/04/19
Re: 2.9.11?, Michael Goffioul, 2007/04/19
Re: 2.9.11?, A S Hodel, 2007/04/18