search for: relativepath

...> <References> > </References> > <Files> > <Filter > Name="Source Files" > Filter="cpp;c;cxx;def;odl;idl;hpj;bat;asm;asmx" > UniqueIdentifier="{4FC737F1-C7A5-4376-A066-2A32D752A2FF}"> > <File > RelativePath="..\..\lib\Target\X86\X86AsmPrinter.cpp"> > </File> > <File > RelativePath="..\..\lib\Target\X86\X86CodeEmitter.cpp"> > </File> > <File > RelativePath="..\..\lib\Target\X86\X86FloatingPoint.cpp"> >...

...;/References> > > <Files> > > <Filter > > Name="Source Files" > > Filter="cpp;c;cxx;def;odl;idl;hpj;bat;asm;asmx" > > UniqueIdentifier="{4FC737F1-C7A5-4376-A066-2A32D752A2FF}"> > > <File > > RelativePath="..\..\utils\TableGen\AsmWriterEmitter.cpp"> > > </File> > > <File > > RelativePath="..\..\utils\TableGen\CodeEmitterGen.cpp"> > > </File> > > <File > > RelativePath="..\..\utils\TableGen\CodeGe...

...00 1.2 > +++ win32/Support/Support.vcproj 15 Nov 2004 08:56:40 -0000 > @@ -183,6 +183,111 @@ > Name="Header Files" > Filter="h;hpp;hxx;hm;inl;inc;xsd" > UniqueIdentifier="{93995380-89BD-4b04-88EB-625FBE52EBFB}"> > + <File > + RelativePath="..\..\include\llvm\Support\AIXDataTypesFix.h"> > + </File> > + <File > + RelativePath="..\..\include\llvm\Support\Annotation.h"> > + </File> > + <File > + RelativePath="..\..\include\llvm\Support\CallSite.h">...

Hi, when I updated the sources today there were several small problems that stopped the windows version from compiling, here are the patches m. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: win32patches.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20041115/34634455/attachment.txt>

...========================== > --- win32/Analysis/Analysis.vcproj (revision 51223) > +++ win32/Analysis/Analysis.vcproj (working copy) > @@ -353,6 +353,14 @@ >> > </File> > <File > + RelativePath="..\..\lib\Analysis > \LibCallAliasAnalysis.cpp" > + > > + </File> > + <File > + RelativePath="..\..\lib\Analysis > \LibCallSemantics.cpp" >...

attached is the diff of vcprojs that need to be changed to fix the VS build as of revision: 51224. I don't know if this catches all the missing bits, but this does build all the way through. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: msvs.patch URL:

Hi all, I have a new pre-reelase (with a GPG signature) up here: http://mega-nerd.com/tmp/flac-1.3.3rc1.tar.xz http://mega-nerd.com/tmp/flac-1.3.3rc1.tar.xz.asc This code is built from commit 10a28d482a8e48b806f61ab766992b2add98ec43 plus another commmit to change the version numbers which I will not be pushing to the public repo before the final release. Note that audio files encoded

Razvan Aciu wrote: > As I saw from the mailing list the MSVC 2005 patches were made to take into > account the new files from the development branch, files which are not in > the 2.3 release. So for now the below patch is the only one functional for > the release. If I am wrong, please someone correct me. > > If someone can make a 2005 patch for the release branch, it is ok.

On Oct 10, 2008, at 1:44 PM, Óscar Fuentes wrote: > OvermindDL1 <overminddl1 at gmail.com> writes: > > [snip] > >> On this first compile everything compiled except for llc and lli, >> which did not link due to: >> unresolved external symbol "class llvm::FunctionPass * __cdecl >> llvm::createPBQPRegisterAllocator(void)" > > That is because

OvermindDL1 <overminddl1 at gmail.com> writes: [snip] > On this first compile everything compiled except for llc and lli, > which did not link due to: > unresolved external symbol "class llvm::FunctionPass * __cdecl > llvm::createPBQPRegisterAllocator(void)" That is because the lib/CodeGen project file is missing PBQP.cpp. [snip] > On Fri, Oct 10, 2008 at 2:11

...not matter where in the section, just stick it with the rest of the file xml nodes in the CodeGen.vcproj file. No clue if anything else is missing, but it all builds fine with these: These two go in the Name="Source Files" section, search for Name="Source Files" <File RelativePath="..\..\lib\CodeGen\PBQP.cpp" > </File> <File RelativePath="..\..\lib\CodeGen\RegAllocPBQP.cpp" > </File> And this goes in the Name="Header Files" section as a child node, again, just search for Name="Header Files"...

Adding the different header files is not strictly required but certain features (Search in solution for example) in VS work better when they are there... m. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: diff.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050103/9de97790/attachment.txt>

...c/share/grabbag/grabbag_static.vcproj --- a/src/share/grabbag/grabbag_static.vcproj Wed Jan 2 13:49:55 2013 +++ b/src/share/grabbag/grabbag_static.vcproj Tue Mar 12 09:46:01 2013 @@ -163,6 +163,10 @@ UniqueIdentifier="{4FC737F1-C7A5-4376-A066-2A32D752A2FF}" > <File + RelativePath=".\alloc.c" + > + </File> + <File RelativePath=".\cuesheet.c" > </File>

Janne Hyv?rinen wrote: > With the sources as they are compiling produces these errors (this on > MSVC 2012 SP1 Express): > > Error 1 error LNK2001: unresolved external symbol > _FLAC__bitreader_bits_left_for_byte_alignment > G:\Programming\flac-1.3.0pre2\src\flac\libFLAC_static.lib(stream_decoder.obj) Ben Alison is working on tthis. Lets allow that work to come to a

...h as "..\..\include". Is it better to >> leave them as is or to change to something like "$(SolutionDir)include"? > > That sounds like a good idea. I opened libFLAC_static.vcproj in a text editor and it turns out that it contains relative paths anyway: <File RelativePath="..\..\include\FLAC\stream_encoder.h"></File> So replacing relative paths in "AdditionalIncludeDirectories" entries seems rather pointless, sorry. >> Is it better to remove these files from Makefile and .vcproj files, or to leave them? >> I don't thin...

lvqcl wrote: > 1) > Current MSVC solution (FLAC.sln and numerous .vcproj files) was made with > VC2005 Express and doesn't allow to build 64-bit files/libraries. > > IMHO it's time to add 64-bit support for MSVC builds, but AFAIK only Visual Studio > 2012/2013 Express are free and allow to build 64-bit files. > > VS 2005/2008 use .vcproj files, and VS

...it better to > >> leave them as is or to change to something like "$(SolutionDir)include"? > > > > That sounds like a good idea. > > I opened libFLAC_static.vcproj in a text editor and it turns out that it > contains relative paths anyway: > <File RelativePath="..\..\include\FLAC\stream_encoder.h"></File> > So replacing relative paths in "AdditionalIncludeDirectories" entries seems > rather pointless, sorry. Ok, you know more about this than me. > >> Is it better to remove these files from Makefile and .vcpro...

...Rearrange error handling in IKnownFolder::GetFolderDefinition. shell32: Use a helper function to get DWORDs from registry. shell32: Use a helper function to allocate strings from the registry. shell32: Also return ParentFolder ID in GetFolderDefinition. shell32: Also return RelativePath in GetFolderDefinition. shell32: Fall back on CSIDL path for knownfolders without a path in the registry. Andrey Gusev (5): po: Fix a mistake in Dutch translation. x3daudio1_4: Add stub dll. x3daudio1_5: Add stub dll. x3daudio1_3: Add stub dll. po: Update Ukrain...

Hello, My company is looking for someone familiar with Rails, but *really* familiar with front-end web development; CSS, Javascript (Ajax + +good), and one of the XXp templating languages. We''re migrating a rusty J2EE-ish app to Rails, and we need someone who can flip between controller work and view development with ease. Very relaxed, flexible work atmosphere--we value