Skip to content

Commit

Permalink
Windows build scripts use fftw 3.3.4 [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
@markummitchell-tu
markummitchell-tu committed Oct 9, 2016
1 parent 9ab136f commit 9fbbea5
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 1 deletion.
2 changes: 1 addition & 1 deletion dev/windows/setup_win10.bat
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

rem Variables must go BEFORE vcvars32.bat which breaks all later SETs
set QTDIR=C:\Qt\5.6\msvc2013
set FFTW_HOME=%USERPROFILE%\fftw-3.3.3
set FFTW_HOME=%USERPROFILE%\fftw-3.3.4
set LOG4CPP_HOME=%USERPROFILE%\log4cpp_null

rem mingw
Expand Down
12 changes: 12 additions & 0 deletions dev/windows/setup_win10_64.bat
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
@echo off

rem Variables must go BEFORE vcvars32.bat which breaks all later SETs
set QTDIR=C:\Qt64\5.6\msvc2013_64
set FFTW_HOME=%USERPROFILE%\fftw-3.3.4
set LOG4CPP_HOME=%USERPROFILE%\log4cpp_null

rem mingw
set PATH=%QTDIR%/bin;%PATH%

rem PATH must point to .../Microsoft Visual Studio 14.0/vc/vcvars32.bat
vcvarsall.bat

This comment has been minimized.

Sign in to view

Copy link
@crayxt

crayxt Oct 9, 2016

Collaborator

Are you preparing to provide 64-bit build of engauge? I do have 64-bit log4cpp regular and debug builds.

This comment has been minimized.

Sign in to view

Copy link
@markummitchell

markummitchell Oct 9, 2016

Owner

I am working on building for Windows 10/64. I tried to install Windows 7/64 but had problems.

I have a log4cpp_null project on github that I use for building a log4cpp replacement. It was created since OSX is not happy about logging files. I'll probably use that, since it has a portable 'pro' file.

1 comment on commit 9fbbea5

@markummitchell
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Microsoft has made building of a 64 bit version much too time consuming. Installation of VS2013 involves 'program compatibility bugs' and the workarounds are not working. I will retry in a few months.

Please sign in to comment.