llvm dev - Mar 2007 - [LLVMdev] x86 in win32 folder

Is there any special reason only x86 code is implemented in win32 folder unlike
lib\Target folder which contains codes for other architectures?

Thank you.
Seung Jae Lee

Seung Jae Lee wrote:
> Is there any special reason only x86 code is implemented in win32 folder
unlike lib\Target folder which contains codes for other architectures?
No reason beyond the fact that windows is more or less only x86/x64. If you want
to add more targets to the visual
studio project files it shouldn't be very difficult. You can copy the custom
build rules for the .td files in the x86
project. The rest is just adding the .cpp and .h files and setting the include
paths etc. to the same as in the x86 project.

m.

Might I suggest the following tool for setting-up/maintaining the  
Visual Studio project files. It makes setting them up with all the  
right build options and include paths much, much easier. =)

http://sourceforge.net/projects/xpj

--
Christopher Lamb
christopher.lamb at gmail.com


On Mar 28, 2007, at 3:06 AM, Morten Ofstad wrote:
> Seung Jae Lee wrote:
>> Is there any special reason only x86 code is implemented in win32  
>> folder unlike lib\Target folder which contains codes for other  
>> architectures?
>
> No reason beyond the fact that windows is more or less only x86/ 
> x64. If you want to add more targets to the visual
> studio project files it shouldn't be very difficult. You can copy  
> the custom build rules for the .td files in the x86
> project. The rest is just adding the .cpp and .h files and setting  
> the include paths etc. to the same as in the x86 project.
>
> m.
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20070328/6bfd2b70/attachment.html>