I tried building gen-mpir alone and got this error:
1>------ Build started: Project: gen-mpir, Configuration: Debug x64 ------
1> gen-mpir.c
1>LINK : fatal error LNK1104: cannot open file 'kernel32.lib'
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
I don't know where to find "a public Visual C++ or Windows SDK forum" do
you?
If I open Project->Properties->Configuration Properties->VC++ Directiories
below is what I see:
Executable Directories:
$(VCInstallDir)bin\x86_amd64;$(VCInstallDir)bin;$(WindowsSdkDir)bin\NETFX
4.0
Tools;$(WindowsSdkDir)bin;$(VSInstallDir)Common7\Tools\bin;$(VSInstallDir)Common7\tools;$(VSInstallDir)Common7\ide;$(ProgramFiles)\HTML
Help
Workshop;$(FrameworkSDKDir)\bin;$(FrameworkSDKDir)\lib\win64;$(MSBuildToolsPath32);$(FxCopDir);$(PATH)
Include Derectories:
$(VCInstallDir)include;$(VCInstallDir)atlmfc\include;$(WindowsSdkDir)include;$(FrameworkSDKDir)\include;
Reference Directories:
$(VCInstallDir)atlmfc\lib\amd64;$(VCInstallDir)lib\amd64
Library Directories:
$(VCInstallDir)lib\amd64;$(VCInstallDir)atlmfc\lib\amd64;$(WindowsSdkDir)lib\x64;
Source Directories:
$(VCInstallDir)atlmfc\src\mfc;$(VCInstallDir)atlmfc\src\mfcm;$(VCInstallDir)atlmfc\src\atl;$(VCInstallDir)crt\src;
Exclude Directories:
$(VCInstallDir)include;$(VCInstallDir)atlmfc\include;$(WindowsSdkDir)include;$(FrameworkSDKDir)\include;$(MSBuildToolsPath);$(MSBuildToolsPath32);$(VCInstallDir)atlmfc\lib\amd64;$(VCInstallDir)lib\amd64;
I'm doing my best to provide useful information here but am not sure if I am
achieving that.
Regards
Chris Saunders
--------------------------------------------------
From: "Cactus" <rieman...@gmail.com>
Sent: Sunday, June 13, 2010 2:32 AM
To: "mpir-devel" <mpir-devel@googlegroups.com>
Subject: [mpir-devel] Re: Building MPIR for Windows x64 with Visual Studio
2010 Express
On Jun 13, 5:47 am, "Chris Saunders" <e...@mountaincable.net> wrote:
I later tried to double click on mpir.h in the Solution Explorer and got
a
dialog box that said "The document cannot be opened. It has been
renamed,
deleted or moved".
Regards
Chris Saunders
--------------------------------------------------
From: "Chris Saunders" <e...@mountaincable.net>
Sent: Sunday, June 13, 2010 12:38 AM
To: "mpir-devel" <mpir-devel@googlegroups.com>
Subject: Re: [mpir-devel] Re: Building MPIR for Windows x64 with Visual
Studio 2010 Express
>>For a Visual C++ project open Properties->Configuration Properties-
>>General and change Platform Toolset from the default v100 to
>>Windows7.1 SDK.
> I tried this setting and then tried to build again. The build failed
> again. The errors that I got were all similar so I'm just going to show
> one:
> 6>..\..\randmt.c(28): fatal error C1083: Cannot open include file:
> 'mpir.h': No such file or directory
> 6> randmts.c
> I did search for the file(using windows search with Explorer targeted
> to
> the MPIR project directory) and I could not find mpir.h. I
> re-extracted
> mpir-2.1.1-rc1.tar.gz into another directory and could not find mpir.h
> in
> that directory either.
> Regards
> Chris Saunders
> --
> You received this message because you are subscribed to the Google
> Groups
> "mpir-devel" group.
> To post to this group, send email to mpir-de...@googlegroups.com.
> To unsubscribe from this group, send email to
> mpir-devel+unsubscr...@googlegroups.com.
> For more options, visit this group at
>http://groups.google.com/group/mpir-devel?hl=en.- Hide quoted text -
- Show quoted text -
Your problem is NOT mpir.h - this doesn't exist because gen-mpir,
which generates mpir.h, fails to build so mpir.h is not created.
The issue is why Visual Studio cannot find a standaard library -
kernel32.lib. As I said earlier, I suspect the library path is not
being set up correcctly.
The thing to focus on is not building all of mpir at the moment but
just that of getting gen-mpir to build. I think it may be necessary
to get the output when building gen-mpir in its x64|release
configuration and ask on a public Visual C++ or Windows SDK forum
about _this_ failure and why kernel32.lib is not being foound.
Right now I believe the other failures are all caused by this gen-mpir
failure.
Brian
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-de...@googlegroups.com.
To unsubscribe from this group, send email to
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-de...@googlegroups.com.
To unsubscribe from this group, send email to
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
