search for: proj_src_root

...+ $(Echo) "PreConditions: " '$(PreConditions)' 2) In Makefile.config.in PROJ_SRC_DIR define for LLVM build mode as PROJ_SRC_DIR := $(subst //,/,$(LLVM_SRC_ROOT)/$(patsubst $(PROJ_OBJ_ROOT)%,%,$(PROJ_OBJ_DIR))) and for other project build mode as PROJ_SRC_DIR := $(subst //,/,$(PROJ_SRC_ROOT)/$(patsubst $(PROJ_OBJ_ROOT)%,%,$(PROJ_OBJ_DIR))) This two definition is equal (in LLVM build mode $(LLVM_SRC_ROOT) == $(PROJ_SRC_ROOT) ) and have common problem. If generated Makefile.config used in Makefile not in root of project object tree $(PROJ_SRC_DIR) != $(PROJ_SRC_ROOT) it set PROJ_SRC...

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron

Hi LLVM-folks, is there a way to use the llvm-build tool for out-of-tree projects? Makefile.rules supposes llvm-build to be located in PROJ_SRC_ROOT and this does not hold for out-of-tree projects, the same applies to Makefile.llvmbuild that is searched for in PROJ_OBJ_ROOT. I think PROJ_SRC_ROOT should be replaced by LLVM_SRC_ROOT and PROJ_OBJ_ROOT should be replaced by LLVM_OBJ_ROOT, right? Ciao, Fabian -------------- next part -------------...

...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 put it...

...VERB) $(RM) -f $@ @echo "---------------------------------------------------------------" >> $@ @echo ">>> ========= '$(RELDIR)/$*' Program" >> $@ @echo "---------------------------------------------------------------" >> $@ - $(PROJ_SRC_ROOT)/TEST.libcalls.Makefile @-$(LOPT) -simplify-libcalls -stats -debug-only=simplify-libcalls \ -time-passes -disable-output $< 2>>$@ summary:

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 because it w...

...so" file. I compiled the runtime library using MAKE and tried on both Windows and Mac, but the compiling can not be done properly. I got the following error message: ------------------------------ make: Entering directory `C:/llvm/runtime' ../Makefile.config.in:59: *** Projects must define PROJ_SRC_ROOT. Stop. make: Leaving directory `C:/llvm/runtime' ----------------------------- How to fix these errors? Is these any other way to compile the runtime library and generate "profile_rt.so" file? Many thanks. Yafan -------------- next part -------------- An HTML attachment was scrubbe...

...r example, llvm-java use llvm-java/autoconf/install-sh is more correct (synchronized version with other autoconf files and configure in project sources) Is patch replacing INSTALL_SH := $(LLVM_SRC_ROOT)/autoconf/install-sh MKDIR := $(LLVM_SRC_ROOT)/autoconf/mkinstalldirs by INSTALL_SH := $(PROJ_SRC_ROOT)/autoconf/install-sh MKDIR := $(PROJ_SRC_ROOT)/autoconf/mkinstalldirs acceptable? LLVM (including Stacker, sample), llvm-java build and installed with patch and without problems. llvm-test have same install-sh and mkinstalldirs files as Stacker. Vladimir -------------- next part ----------...

...=========================== --- Makefile.rules (revision 45533) +++ Makefile.rules (working copy) @@ -483,8 +483,9 @@ ProgInstall = $(INSTALL) $(Install.StripFlag) -m 0755 ScriptInstall = $(INSTALL) -m 0755 DataInstall = $(INSTALL) -m 0644 -TableGen = $(TBLGEN) -I $(PROJ_SRC_DIR) -I$(PROJ_SRC_ROOT)/include \ - -I $(PROJ_SRC_ROOT)/lib/Target +TableGen = $(TBLGEN) -I $(call SYSPATH, $(PROJ_SRC_DIR)) \ + -I $(call SYSPATH, $(PROJ_SRC_ROOT)/include) \ + -I $(call SYSPATH, $(PROJ_SRC_ROOT)/lib/Target) Archive = $(AR) $(AR.Flags) LArchive...

...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_ROOT and V...

...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 in the LL...

...-------------------------------------------------------------" >> > $@ > @echo ">>> ========= '$(RELDIR)/$*' Program" >> $@ > @echo > "---------------------------------------------------------------" >> > $@ > - $(PROJ_SRC_ROOT)/TEST.libcalls.Makefile > @-$(LOPT) -simplify-libcalls -stats -debug-only=simplify-libcalls \ > -time-passes -disable-output $< 2>>$@ > summary: > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu ht...

...kefile =================================================================== --- TEST.libcalls.Makefile (revision 92749) +++ TEST.libcalls.Makefile (working copy) @@ -23,10 +23,10 @@ $(PROGRAMS_TO_TEST:%=Output/%.$(TEST).report.txt): \ Output/%.$(TEST).report.txt: Output/%.linked.rbc $(LOPT) \ $(PROJ_SRC_ROOT)/TEST.libcalls.Makefile + $(VERB) $(RM) -f $@ @echo "---------------------------------------------------------------" >> $@ @echo ">>> ========= '$(RELDIR)/$*' Program" >> $@ @echo "--------------------------------------------------------...

...on both > Windows and Mac, but the compiling can not be done properly. I got the > following error message: > ------------------------------ > make: Entering directory `C:/llvm/runtime' > ../Makefile.config.in:59 <http://Makefile.config.in:59>: *** Projects > must define PROJ_SRC_ROOT. Stop. > make: Leaving directory `C:/llvm/runtime' > ----------------------------- > How to fix these errors? Is these any other way to compile the runtime > library and generate "profile_rt.so" file? It looks like llvm/runtime is missing CMakeFile.txt's, and probabl...

...ay to completely disable JIT and interpret the code instead? Foivos On 06/11/2012 04:51 PM, Nicolas Geoffray wrote: > 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

Hi Fabian, > is there a way to use the llvm-build tool for out-of-tree projects? > Makefile.rules supposes llvm-build to be located in PROJ_SRC_ROOT and this does > not hold for out-of-tree projects, the same applies to Makefile.llvmbuild that > is searched for in PROJ_OBJ_ROOT. I think PROJ_SRC_ROOT should be replaced by > LLVM_SRC_ROOT and PROJ_OBJ_ROOT should be replaced by LLVM_OBJ_ROOT, right? for an out-of-tree build you can use...

This is what I get while trying to run 'make TEST=libcalls' in the top dir of test-suite: make[1]: Entering directory `/home/gregory/thesis/llvm/projects/test-suite/SingleSource' make[2]: Entering directory `/home/gregory/thesis/llvm/projects/test-suite/SingleSource/UnitTests' make[3]: Entering directory

On Mon, 2005-02-14 at 20:53, Chris Lattner wrote: > On Mon, 14 Feb 2005, Reid Spencer wrote: > > > Personally, I don't think LLVM projects should need much in the way of > > autoconf stuff. They certainly don't need to replicate things like > > install-sh and mkinstalldirs. I'd vote for taking these out of the > > projects rather than making the makefiles

...cs yet because I am still thinking about what to write. > - I probably made some mistakes in setting up the makefile rules - that > is what took the most time - so it will merit heightened scrutiny. > > +++ unittests/Makefile.unittest (revision 0) [...] +VPATH=$(PROJ_SRC_DIR) $(PROJ_SRC_ROOT)/unittests That doesn't look like a valid path to me. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20081230/1702d213/attachment.html>

On Mon, 14 Feb 2005, Reid Spencer wrote: > Personally, I don't think LLVM projects should need much in the way of > autoconf stuff. They certainly don't need to replicate things like > install-sh and mkinstalldirs. I'd vote for taking these out of the > projects rather than making the makefiles deal with them. I think in > most cases these are just historical artifacts