[cmake-developers] VS2010 fortran composer

Biddiscombe, John A. biddisco at cscs.ch
Wed Mar 9 13:49:57 EST 2011


Thanks

It's a bit of a hack, but testing for the target name and overriding the output path seems to work.
This gets me past the trycompile step so now projects are being generated from scratch.

      if (this->Name=="cmTryCompileExec") {
        std::string path = cmsys::SystemTools::GetFilenamePath(this->PathToVcxproj);
        (*this->BuildFileStream ) << " OutputFile=\""
          << cmsys::SystemTools::ConvertToWindowsOutputPath(path.c_str()).c_str()
          << "\\" << this->Name << ".exe\"/>\n";
      }
      else {
        (*this->BuildFileStream ) << "/>\n";
      }

I'll stick with this for now - if there's a better way I'll no doubt find out eventually ...

JB


From: Bill Hoffman [mailto:bill.hoffman at kitware.com]
Sent: 09 March 2011 13:54
To: Biddiscombe, John A.
Cc: cmake-developers at cmake.org
Subject: Re: RE: VS2010 fortran composer


http://software.intel.com/en-us/forums/showthread.php?t=80773

That Guy seemed to change it...

sent from my phone
On Mar 9, 2011 4:29 AM, "Biddiscombe, John A." <biddisco at cscs.ch<mailto:biddisco at cscs.ch>> wrote:
>
>
> OK, that is odd... Is there a way to change that in the project files
>
> that you generate?
>
>
>
> Seems like it would be odd for the C/C++ stuff to end up in Debug, and
>
> the fortran to be in X64/Debug...
>
>
>
> It does not appear to be something I can control.
>
>
>
> JB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20110309/5abcb578/attachment.html>


More information about the cmake-developers mailing list