[LLVMdev] x86 in win32 folder
Christopher Lamb
christopher.lamb at gmail.com
Wed Mar 28 08:22:06 PDT 2007
I don't want to drive this too off topic, but I should be clear that
I wasn't suggesting that the LLVM project adopt XPJ as it's official
config file format for Visual Studio. I have found it useful to use
XPJ to generate the initial VS projects for a code base that doesn't
already have VS projects. I also find it nice to be able to see all
of the config options in a flat, human readable file rather than a
GUI, but this is certainly personal preference.
On Mar 28, 2007, at 9:46 AM, Jeff Cohen wrote:
> It's not clear it offers any real benefits. The project files
> already exist. To use this, I would have to throw them away and
> create new XML files by hand. I would have to maintain them by
> hand also, whereas the project files are maintainable from within
> Visual Studio, i.e. via an integrated GUI interface.
>
> And to comment on supporting other targets: No reason it can't be
> done, other than Windows doesn't run on them, but be aware that
> they have never been compiled with VC++ and there may be issues
> with the code that need resolving before it successfully compiles
> with VC++.
>
> Christopher Lamb wrote:
>> 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
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
--
Christopher Lamb
christopher.lamb at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070328/e01a4321/attachment.html>
More information about the llvm-dev
mailing list