search for: proj_

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: 1081 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050214/a838982e/attachment....

...maintained. For example, SAFECode doesn't have its own build system; it uses LLVM's, and it does so without being a "patch" to the LLVM source tree. You can put the SAFECode source code anywhere you like, use LLVM-style Makefiles in its source code, and build it. All of the PROJ_SRC_ROOT, PROJ_OBJ_ROOT magic in the autoconf build system is what permits that feature to work. Do you intend to keep this functionality when you replace autoconf with cmake, or will all projects that want to use the LLVM build system need to place their source code in the LLVM source tree? To...

The proposed makefile changes have been committed. If you are working from CVS head and you use the LLVM Makefile System in your own project, please make a note of the following: 1. If your makefiles use any BUILD_* variables, they now need to be prefixed with PROJ_ instead of BUILD_. For example, BUILD_SRC_ROOT is now PROJ_SRC_ROOT. 2. There are additional requirements for projects. Please review this file: http://illuvium.net/src/projects/sample/Makefile.common.in On Fri, 2005-01-14 at 09:55, Reid Spencer wrote: > Hi, > &...

The proposed makefile changes have been committed. If you are working from CVS head and you use the LLVM Makefile System in your own project, please make a note of the following: 1. If your makefiles use any BUILD_* variables, they now need to be prefixed with PROJ_ instead of BUILD_. For example, BUILD_SRC_ROOT is now PROJ_SRC_ROOT. 2. There are additional requirements for projects. Please review this file: http://illuvium.net/src/projects/sample/Makefile.common.in as it contains the complete list of variables you need to set and pro...

...e: > The proposed makefile changes have been committed. If you are working > from CVS head and you use the LLVM Makefile System in your own project, > please make a note of the following: > > 1. If your makefiles use any BUILD_* variables, they now need to be > prefixed with PROJ_ instead of BUILD_. For example, > BUILD_SRC_ROOT is now PROJ_SRC_ROOT. > > 2. There are additional requirements for projects. Please review > this file: > http://illuvium.net/src/projects/sample/Makefile.common.in > as it contains the complete list of variable...

...to use them. I propose removing them or using names prefixed with llvm_ to ensure their use is only for llvm 2. BUILD_SRC_DIR and BUILD_OBJ_DIR are poorly named. This has been a source of confusion for me personally and probably for others. They should really be PROJ_SRC_DIR and PROJ_OBJ_DIR to indicate they pertain to the project's src/obj dir not LLVM's 3. The LLVM makefiles require a Makefile.config in the project. I'm going to try to make that optional because some projects can just use LLVM's Makefile.config....

...or example, > SAFECode doesn't have its own build system; it uses LLVM's, and it > does so without being a "patch" to the LLVM source tree. You can put > the SAFECode source code anywhere you like, use LLVM-style Makefiles > in its source code, and build it. All of the PROJ_SRC_ROOT, > PROJ_OBJ_ROOT magic in the autoconf build system is what permits > that feature to work. > > Do you intend to keep this functionality when you replace autoconf > with cmake, or will all projects that want to use the LLVM build > system need to place their source code i...

...problem. Build was unable to locate llvm-build because it was looking for it in path/to/vmkit_src/utils/llvm-build while it was located in path/to/llvm_src/utils/llvm-build Actually llvm-build's path is defined by the path/to/llvm_src/Makefile.rules and looks like this LLVMBuildTool := $(PROJ_SRC_ROOT)/utils/llvm-build/llvm-build however in the case of vmkit it should be LLVMBuildTool := $(LLVM_SRC_ROOT)/utils/llvm-build/llvm-build i Also noticed that in the vmkit's generated (by configure) Makefile.config there are defined PROJ_SRC_ROOT and VMKIT_SRC_ROOT as well as PROJ_OBJ_RO...

Dear All, Will the LLVM project system (the extension to the build system that allows sub-projects to reuse the LLVM Makefiles) be maintained long term, or is the slow push to CMake intending to deprecate this functionality? We used this feature a lot for research projects at UIUC, but if the current maintainers of the build system are planning on deprecating it, I'll have my students

Hi Nicolas, it looks like there are missing things $ more lib/j3/LLVMRuntime/LLVMRuntime.inc // Generated by llvm2cpp - DO NOT MODIFY! Module* makeLLVMModuleContents(Module *mod) { mod->setModuleIdentifier("<stdin>"); // Type Definitions // Function Declarations // Global Variable Declarations // Constant Definitions // Global Variable Definitions // Function

Thanks Favios for finding the problem! I have applied a patch to Makefile.rules, hopefully it now works without you editing some files. About VMKIT_SRC_ROOT and PROJ_SRC_ROOT, it is fine to have both in the code. I find it clearer to use VMKIT_SRC_ROOT. Nicolas On Sun, Jun 10, 2012 at 10:09 PM, Foivos S. Zakkak <foivos at zakkak.net>wrote: > Hi Nicolas, > > I finally found the root of the problem. Build was unable to locate > llvm-build beca...