[LLVMdev] building llvm on Windows

[Chris Lattner]

On May 11, 2008, at 12:59 PM, Razvan Aciu wrote:

> I tried to compile on Windows ( using the win32/llvm.sln in MSVC  
> Express
> 2008 ) the new 2.3 branch and here are the results:

It would be great to get any windows improvements into the 2.3 release  
if possible.

> 1. I needed to copy the file Configure.exe.embed.manifest to
> Configure.exe.intermediate.manifest . This is a bug from the  
> previous llvm
> release (2.2)

Please send a patch.

> 2. I copied the file SimplifyLibCalls.cpp from lib/Transforms/Scalar  
> to
> lib/Transforms/IPO. I think the position of this file was updated  
> but the
> MSVC project wasn't.

Please update the project file and send a patch for it.

> 3. I put a "return SDOperand();" on X86ISelLowering.cpp, on function
> "SDOperand X86TargetLowering::LowerVAARG(SDOperand Op, SelectionDAG  
> &DAG)"
> after "abort()", to make compiler happy to compile it.

This went into mainline, Tanya, can we pull this patch into 2.3?
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080512/062268.html

> 4. I needed to give "Build Solution" more times, because there are  
> some
> incorrect dependencies between projects and some of them expect  
> results from
> the future builded ones.

Please fix them :)

> After over 4500 warnings, I think most of them because of the  
> automatically
> generated code, I succeded to compile almost all the projects,  
> except opt
> and bugpoint. At these two I had an error:
>
> error LNK2019: unresolved external symbol "class llvm::FunctionPass *
> __cdecl llvm::createLibCallAliasAnalysisPass(class llvm::LibCallInfo  
> *)"
> (? 
> createLibCallAliasAnalysisPass 
> @llvm@@YAPAVFunctionPass at 1@PAVLibCallInfo at 1@@Z)
> referenced in function "public: __thiscall `anonymous
> namespace'::ForcePassLinking::ForcePassLinking(void)"
> (??0ForcePassLinking@?A0xd1580448@@QAE at XZ)
>
> which I wasn't able to fix it.

This sounds like lib/Analysis/LibCallAliasAnalysis.cpp needs to be  
added to the project file.

> I hope these will be fixed on the final 2.3 release so it can be  
> compiled
> out of the box on MSVC Express 2008.

We would love to have this fixed, but since most of the core  
developers aren't using VC++, the only way it will get fixed for LLVM  
2.3 is if someone sends up patches.  Can you please do this?

-Chris