search for: llpm

...ndently reusable, but we don't have effective tools for managing and maintaining proper physical dependencies to make that happen. There are actually a bunch of things in Support that I wish could be independently reused. Like if I want to write up a little program, I really wish I could do $ llpm install StringRef ArrayRef raw_ostream MemoryBuffer and then have it put those relevant modules and their dependencies in a local `deps/` (or whatever) directory so that I can then just include them in my build. -- Sean Silva -------------- next part -------------- An HTML attachment was scrubbed...

...t have effective tools for managing and maintaining > proper physical dependencies to make that happen. > > There are actually a bunch of things in Support that I wish could be > independently reused. Like if I want to write up a little program, I really > wish I could do > > $ llpm install StringRef ArrayRef raw_ostream MemoryBuffer > > and then have it put those relevant modules and their dependencies in a > local `deps/` (or whatever) directory so that I can then just include them > in my build. > > -- Sean Silva -- 此致 礼 罗勇刚 Yours sincerel...

Going to be interesting layering issues if you do the latter. Then you have CodeGen depending upon DebugInfo instead of just a header in Support. -eric On Fri, Jun 28, 2013 at 11:08 AM, 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> wrote: > For example, > ELF.h MachO.h and COFF.h > should moved into Object directory with new name. > and Dwarf.h should moved into DebugInfo

For example, ELF.h MachO.h and COFF.h should moved into Object directory with new name. and Dwarf.h should moved into DebugInfo directory. 2013/6/29 Eric Christopher <echristo at gmail.com>: > Where would you like to move them? > > -eric > > On Fri, Jun 28, 2013 at 10:38 AM, 罗勇刚(Yonggang Luo) > <luoyonggang at gmail.com> wrote: >> From my point of view, the