Kai Sterker wrote:
On 9/27/06, Brad King <[EMAIL PROTECTED]> wrote:
I'm not sure this is a bug. The msys prefix has special meaning only
for some native msys tools. The fact that you have chosen to install
other things there is no different than installing them in
c:/my/random/path (I think,
On 9/27/06, Brad King <[EMAIL PROTECTED]> wrote:
I'm not sure this is a bug. The msys prefix has special meaning only
for some native msys tools. The fact that you have chosen to install
other things there is no different than installing them in
c:/my/random/path (I think, but I'm not an MSYS
Hi,
I'm using CPack to generate a Windows installer for a simulation
package. The code was compiled using VS 2005, and I'd like NSIS to
execute the Microsoft-supplied vcredist_x86.exe during install. How
would I do this?
I noticed the CPACK_NSIS_EXTRA_INSTALL_COMMANDS variable, but I
haven't foun
Kai Sterker wrote:
> But cmake cannot find the headers, (or libraries in /usr/local/lib),
> because it does know nothing about the UNIX-like structure of MSYS.
>
> So the problem is not that there is something wrong when running cmake
> from a MSYS shell instead of a Windows command prompt. It beh
Arjen Markus wrote:
> Like I promised, here is the information I have on this bug:
[snip]
> As you can see, the source file is given with the native (Windows-style)
> path, but the object file is specified with forward slashes. This is what
> causes the compiler to complain.
Try adding this to you
Axel Roebel wrote:
Hello,
On Wednesday 27 September 2006 07:49, [EMAIL PROTECTED] wrote:
I don't think it matters whether the static library is linked with an
executable or a shared library. Certainly linking to an external shared
library has worked for me recently without me hav
On 2006-09-27 10:42+0200 Axel Roebel wrote:
Hello,
On Wednesday 27 September 2006 07:49, [EMAIL PROTECTED] wrote:
I don't think it matters whether the static library is linked with an
executable or a shared library. Certainly linking to an external shared
library has worked for me recently wi
On Wed, Sep 27, 2006 at 10:42:30AM +0200, Axel Roebel wrote:
> IF("${CMAKE_SYSTEM_PROCESSOR}" STREQUAL "x86_64")
That is not correct. Every shared lib should be compiled with fPIC, on
x86_64 or not. Yes, shared libs with TEXTREL can work on x86, but it
doesn't mean that it's OK to compile them with
Littlejohn, Todd wrote:
> I am currently working on a project that auto-generating code based on a
> data model defined using XSD/XML. The code generator I have developed
> is using CMake to make the code generator. Next CMake is used to
> generate the C++ and Java data models. The problem I am
Hello,
On Wednesday 27 September 2006 07:49, [EMAIL PROTECTED] wrote:
> I don't think it matters whether the static library is linked with an
> executable or a shared library. Certainly linking to an external shared
> library has worked for me recently without me having to do anything
> special.
10 matches
Mail list logo
