search for: build_obj_root

Folks, If you're working from CVS sources and have updated recently, you should know that the Makefiles now place the tools in a different directory. This may affect your path. Three changes were made in resolving PR456: 1. $BUILD_OBJ_ROOT/lib/Debug --> $BUILD_OBJ_ROOT/Debug/lib 2. $BUILD_OBJ_ROOT/tools/Debug --> $BUILD_OBJ_ROOT/Debug/bin 3. Example programs are now placed in $BUILD_OBJ_ROOT/Debug/examples The same is true for Release and Profile builds. So, if you had /path/to/my/build_obj_root/tools/Debug in your path, you...

I found use old BUILD_OBJ_ROOT/BUILD_SRC_ROOT in comment in llvm/Makefile.common and in llvm/projects/Stacker/test/Makefile code. I update it to PROJ_* in attached patches. Vladimir -------------- next part -------------- A non-text attachment was scrubbed... Name: Makefile.common.patch Type: application/octet-stream Size: 1...

...J_ROOT : The root directory containing the built LLVM code. > # > # o BUILD_SRC_DIR : The directory containing the code to build. > # o BUILD_SRC_ROOT : The root directory of the code to build. > # > # o BUILD_OBJ_DIR : The directory in which compiled code will be placed. > # o BUILD_OBJ_ROOT : The root directory in which compiled code is placed. > # > ########################################################################### > > # > # Set the object build directory. By default, it is the current directory. > # > ifndef BUILD_OBJ_DIR > BUILD_OBJ_DIR := $(subst...

Hi John, I have attached my Makefile.config. I noticed that I did'nt have SRC_ROOT and OBJ_ROOT variables defined as such in my environment. But I noticed that this is defined in the Makefile.config by default to the same values. All the same, I tried defining both these variables in my .cshrc, but I still get the same error. The main directory for me is /home/llvm, and I have

...bution (install) as well as providing closure (the distribution can create a distribution of itself) If all that succeeds, you'll see: ===== /proj/work/llvm/build2/LLVM-1.4.tar.gz Ready For Distribution ===== A few things to note: * "make dist-check" can only be run from the BUILD_OBJ_ROOT directory. If you try it somewhere else, you'll be politely told you're off your rocker * "make dist-check" can only be run when BUILD_OBJ_DIR != BUILD_SRC_DIR. If you try it somewhere else, your hard disk will be reformatted (kidding!) * don't run "make dist-check&...

...ains the current set of Makefiles > -# and usually the source code too (unless SourceDir is set). > -# > -# 9. BUILD_SRC_ROOT - The root directory of the source code being compiled. > -# > -# 10. BUILD_OBJ_DIR - The directory where object code should be placed. > -# > -# 11. BUILD_OBJ_ROOT - The root directory for where object code should be > -# placed. > -# > -# For building, > -# LLVM, LLVM_SRC_ROOT = BUILD_SRC_ROOT > +# This file is included by all of the LLVM makefiles. For details on how to use > +# it properly, please see the document MakefileGuide.html...

...perform a "make check" to ensure that all the software builds and that basic sanity checks pass (none have been implemented). If that succeeds, then the directory structure is traversed again for the "distdir" target which copies the distributable sources to a directory in your BUILD_OBJ_ROOT. When that process is complete, the directory is tar'ed and zipped. For the most part, Makefile.rules figures out what is distributable in the same way that it knows what sources to build. However, there are certain things that just don't fit the pattern. This is the part where you come i...

hi, when i change the OBJ_ROOT and recompile the llvm, it's successful. but run following test, then the error occues: ----------------------------------------------------- [yue at RH9 obj]$ make -C ./test/Programs make: Entering directory `/home/yue/llvm/obj/test/Programs' make[1]: Entering directory `/home/yue/llvm/obj/test/Programs/SingleSource' make[2]: Entering directory

...e script identifies the build host and puts it in the $build variable. We use that to determine the basic kind of platform and put it in a variable named $OS. The value of $OS can be: Linux, FreeBSD, Interix, SunOS, Darwin, etc. 2. The platform name is used to create a link from $BUILD_OBJ_ROOT/lib/System/platform to $BUILD_SRC_ROOT/lib/System/$OS 3. All the *.cpp files in lib/System may *only* contain absolutely pure/vanilla platform independent code and they will #include a file of the same name in the "platform" subdirectory. For example lib/System/Path.cpp...

Reid, >As for Interix support in general, I'm having a hard time determining >which variant of Unix Interix implements. It seems to be partially Posix >1 and partially Posix 2 based. Do you have any further information >related to the specific standards supported by Interix? I don't want to >incorrectly categorize the Interix support. I've discussed this subject with