home › Forums › # Technical Support › Cannot get Fuzzylite working with Visual Studio on Win 64
- This topic has 17 replies, 3 voices, and was last updated 7 years, 11 months ago by Juan Rada-Vilela (admin).
December 10, 2014 at 05:50 #1549
I’ve been trying to run fuzzylite 4.0 on my 64 bit windows machine (I also have tried with 5.0 but to no success). I have Visual Studio 2013 installed and have been trying to run one of the example applications. I have included the directory (H:\fuzzylite-4.0\src\fuzzylite) in the Additional Include Directories field, the library (H:\fuzzylite-4.0) in the Additional Libraries Directories field, and the fuzzylite.dll file in the Additional Dependencies field.
The error I get is “error LNK1107: invalid or corrupt file: cannot read at 0x2B8 H:\fuzzylite-3.1\fuzzylite.dll”.
I have read that I should include a .lib file instead of a .dll file with Visual Studio, however I don’t know how to get this file.
Any help would be much appreciated.
LouisDecember 11, 2014 at 00:36 #1551
I have made some progress (I think). I am using Fuzzylite 5.0 now, and have found and included the .lib file in the “Additional Dependencies” field. However when I run the SimpleDimmer example using Visual Studio a blank console window and a pop-up error window appear. The error shown is “The program can’t start because fuzzylite.dll is missing from your computer. Try reinstalling the program to fix this problem”, however fuzzylite.dll is in the directory added to the “Additional Library Directories” field in the project properties. I also tried re-running the CMake procedure and running the program again but the same problem happens. If I specify the .dll file in the “Additional Dependencies” field I get the error “error LNK1107: invalid or corrupt file: cannot read at 0x2B8 H:\fuzzylite-5.0\fuzzylite.dll”.December 15, 2014 at 09:28 #1559
The Additional Libraries Directories needs to be
H:\fuzzylite-4.0\binas that is the directory where the library binaries are located.April 8, 2015 at 12:40 #1739
I’m trying to run fuzzylite on my machine using visual studio 2013. My OS is windows 8.1.
I downloaded the fuzzylite package and created the 6 visual studio projects. What should I do next. When I build those projects I’m getting errors. Can you please help me to configure this.
Iroshani.April 8, 2015 at 13:53 #1740
could you please check the forums for possible solutions?
If the case you cannot find any, could you please post the errors that you are having?
I am not sure if I have compiled fuzzylite on 64bit under Windows, but chances are that I have not and I have the idea that the issue is that there are many warnings that are treated as errors. If such is the case, you should try removing
"-pedantic -Werror"from the
JuanApril 8, 2015 at 15:00 #1741
I searched for related posts. But I couldn’t find any.
I’m getting about 4000 errors for the whole 6 projects. Herewith I have attached an image of errors.
IroshaniApril 8, 2015 at 15:05 #1742
it seems that you cannot compile for C++11. Please, make sure you are not defining
You might want to try first to compile fuzzylite from console as indicated in the webpage (see
www.fuzzylite.com/cpp) and even try building it for C++11 to check whether it can work on your PC.
Cheers.April 10, 2015 at 12:05 #1749
Thank you for your replay.
I tried compiling it from console. But I’m getting an error saying “Could not create named generator NMake Makefiles ‘nmake’ is not recognized as an external or internal command operable program or batch file” How can I install Nmake?
Appreciate if you can provide me a solution.April 10, 2015 at 12:15 #1750
you need to install Visual Studio tools and CMake. If you have installed Visual Studio, then in the group folder in Start Menu you will find a Console that loads up the necessary links and things Windows requires to find nmake. After that, you should be able to compile from Console.
Cheers,April 10, 2015 at 16:42 #1751
I have installed visual studio 2013 and CMake. I’m using windows 8.1
What you mean by group folder in start menu. I cannot find the console.
- You must be logged in to reply to this topic.