Displaying 3 results from an estimated 3 matches for "tool_no_exports".
2015 Jul 22
2
[LLVMdev] (no subject)
Hello,
I have tried a lot fix this error but am not able to can you please
find me a solution am trying to compile the SAFECode in Cygwin Environment
to work for windows.
used make -j4 command to make the files in cygwin i have got this error
make[5]: Leaving directory
'/home/uidr7475/Work/LLVM_OBJ/projects/safecode/tools/clang/include'
/usr/bin/cp: cannot stat
2011 Oct 28
0
[LLVMdev] [cfe-dev] RFC: Upcoming Build System Changes
...e
> clear than what we can put on the CMakeLists.txt or Makefile. I strongly
> doubt that.
Why? Having an independent self contained (and validated) format
should be much more obvious exactly what is supported.
Consider the Makefiles per today. Where do you go to figure out what
things like TOOL_NO_EXPORTS or REQUIRES_EH are supported? We could
document this better, but it would be much less obvious than if there
was one page that documented the LLVMBuild.txt format.
> It is true that `make' has difficulties for handling info unless you
> abide to its rules. That's not the case of cmak...
2011 Oct 28
2
[LLVMdev] [cfe-dev] RFC: Upcoming Build System Changes
Daniel Dunbar <daniel at zuster.org> writes:
> I'm going to briefly summarize my responses here.
>
> On Fri, Oct 28, 2011 at 9:56 AM, Chris Lattner <clattner at apple.com> wrote:
>> On Oct 28, 2011, at 12:54 AM, Óscar Fuentes wrote:
>>> Anyways, if you wish to avoid duplicating info on both Makefile and
>>> CMakeLists.txt there is a simple