search for: developing

I'm trying to compile the latest wine release from source after a fresh linux mint install, and this is what I get when I do './configure' Code: configure: libxcursor development files not found, the Xcursor extension won't be supported. configure: libxi development files not found, the Xinput extension won't be supported. configure: XShape development files not found, XShape

Hello all... I'm trying to compile wine 1.3.21 on my Linux Mint Debian Edition machine, because I'm tired of the antique version available from the repositories. Unfortunately, ./configure always ends with a bunch of WARNINGs and I'm not sure what to do about them. Here's the list it gives me: Code: configure: libxcursor development files not found, the Xcursor extension won't

config.status: linking AUTHORS to dlls/shell32/AUTHORS config.status: linking tools/winewrapper to wine config.status: executing include/stamp-h commands config.status: executing dlls/gdi32/enhmfdrv commands config.status: executing dlls/gdi32/mfdrv commands config.status: executing dlls/kernel32/nls commands config.status: executing dlls/user32/resources commands config.status: executing

Dear LLVM community I need some help please. I want to use LLVM's clang and lld within a MacOSX sandboxed app. This is because sandboxing does not allow calls to /usr/bin/clang. The clang binary works fine to compile a file, but ld64.lld comes up with the error "cannot find framework". However similar arguments using /usr/bin/ld instead of ld64.lld works fine. Here are the

...part. If the backend were staged in a separate tree, this kind of simple review would not be possible, and I would be concerned that developers would be too busy to ever get around to checking out the staging tree. 2. It will allow the backend developers to always develop against TOT. Developing against TOT is the recommended development procedure for anyone working on LLVM, and this is regularly reiterated on the mailing list. If the new backend is included in the main tree, the backend developers will have no choice but to work against TOT. 3. It will make it easier for end users...

This drives me insane on a regular basis. How does one mock system(''blah'') or `blah` ? Adding expectations on Kernel doesn''t do it. Adding expectations on Object just makes me sad: Object.any_instance.expects(:system).with(''ls'') # => #<Mock:0x12b584e>.system(''ls'') - expected calls: 0, actual calls: 1 And this really

Hi Folks, One key goal for Wine 1.0 is that all of its conformance tests run successfully on nearly all systems. We would really like your help in figuring out how close we are to that goal. To that end, if you are comfortable with checking Wine out via git, could you please visit this page: http://wiki.winehq.org/MakeTestFailures and follow the instructions there? (It's really simple;

Just out of curiousity, what OS do most of you use for development? Do you prefer to use WinXP to do your development, and then deploy to a linux server, or do you actually use some distribution of linux (Ubuntu, Debian, Gentoo, etc) for development? Thanks! -- Posted via http://www.ruby-forum.com/.

Error: Code: checking for freetype-config... no checking for freetype2-config... no checking for -lfreetype... not found configure: error: FreeType development files not found. Fonts will not be built. Use the --without-freetype option if you really want this. I tried using the option: Code: ./tools/wineinstall --without-freetype Same error.

Hello all, I have replaced the llvm-gcc shipped with the Xcode by the latest version and I was wondering if I have missed something... (everything *seems* to work). Here's what I did: 0. Checkout LLVM (and clang) + llvm-gcc 1. Build LLVM (with clang) and install into /Developer/usr/local : # mkdir llvmobj # cd llvmobj # CC=gcc-4.2 CXX=g++-4.2 ../llvm/configure

...ged in a separate tree, this kind of > simple review would not be possible, and I would be concerned that > developers would be too busy to ever get around to checking out > the staging tree. > > 2. It will allow the backend developers to always develop against TOT. > > Developing against TOT is the recommended development procedure for > anyone working on LLVM, and this is regularly reiterated on the > mailing list. If the new backend is included in the main tree, > the backend developers will have no choice but to work against TOT. > > 3. It will make...

...d in a separate tree, this kind of > simple review would not be possible, and I would be concerned that > developers would be too busy to ever get around to checking out > the staging tree. > > 2. It will allow the backend developers to always develop against TOT. > > Developing against TOT is the recommended development procedure for > anyone working on LLVM, and this is regularly reiterated on the > mailing list. If the new backend is included in the main tree, > the backend developers will have no choice but to work against TOT. > > 3. It will mak...

...kind of >> simple review would not be possible, and I would be concerned that >> developers would be too busy to ever get around to checking out >> the staging tree. >> >> 2. It will allow the backend developers to always develop against TOT. >> >> Developing against TOT is the recommended development procedure for >> anyone working on LLVM, and this is regularly reiterated on the >> mailing list. If the new backend is included in the main tree, >> the backend developers will have no choice but to work against TOT. >> >...

Hi, i have compile and built the llvm-gcc4 and llvm 1.8a in my machine, but there is some problem about llvm-gcc4. It can not compile a cpp code like this: #include <iostream> using std::cout; using std::endl; int main() { cout << "Hello" << endl; } $llvm-g++ hello.cc -o hello /developer/zsth/llvm-gcc/install/bin/../lib/gcc/i686-pc-linux-gnu/4.0.1/../../..

...for Qualcomms next-generation processors. Our focus is ongoing development of a high performance tool chain used to build the code that drives Qualcomms various modem and applications processor technologies. The right candidate will work on an optimizing linker for multiple targets, with a focus on developing a linker back end for ARM 32- and 64-bit targets. Responsibilities: * Work as part of a small team to design, develop, and deliver new features on a proprietary linker used for Qualcomms embedded projects * Fix bugs in existing code as needed * Coordinate with internal remote ARM LLVM compile...

Good afternoon, I''ve two quick questions for the Ruby/Rails community. 1) Do you use Linux for Ruby or Rails development? 2) If you use Linux, which distro do you normally use to develop? Thank you for your input. :-) -- Posted via http://www.ruby-forum.com/.

The raspberry Pi2 is an armv7a chip (Cortex-A7), the first stage builds fine with the native g++ (if not a little slowly at 10+ hours), but it crashes at some point with this command line: Program arguments: /home/ben/development/llvm/3.6.0/rc2/Phase2/Release/llvmCore-3.6.0-rc2.install/bin/clang -cc1 -triple armv7-unknown-linux-gnueabihf -emit-obj -disable-free -disable-llvm-verifier

Hello guys, I''m developing a new app in Rails, and every now and then I get an ActiveRecord error, I cannot reproduce exactly what triggers it, hope you can help me, or give me tips on debugging this kind of stuff. This time I got the error reporting page, but normally I would just see the 500.html page, with no info about w...

...Thanks! > > On Jan 14, 2009, at 1:29 PM, Jean-Daniel Dupas wrote: > >> >> Le 14 janv. 09 à 21:48, Chris Lattner a écrit : >> >>> >>> On Jan 14, 2009, at 12:44 PM, Graham Wakefield wrote: >>> >>>> Sorry if this is a newb q... I'm developing an application on a >>>> 10.5 machine but want to target the 10.4 SDK. Is there a magic >>>> incantation for the llvm configure script to set the sysroot >>>> path, equivalent to e.g. --with-sysroot "/Developer/SDKs/ >>>> MacOSX10.4u.sdk&q...

...d of >> simple review would not be possible, and I would be concerned that >> developers would be too busy to ever get around to checking out >> the staging tree. >> >> 2. It will allow the backend developers to always develop against TOT. >> >> Developing against TOT is the recommended development procedure for >> anyone working on LLVM, and this is regularly reiterated on the >> mailing list. If the new backend is included in the main tree, >> the backend developers will have no choice but to work against TOT. >> &...