[Bug 819670] Review Request: mingw-llvm - MinGW LLVM libraries
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=819670
--- Comment #9 from Eric Smith <eric(a)brouhaha.com> 2012-05-12 18:57:14 EDT ---
Re:
How does one get something linked against the LLVM-3.0.dll
Pretty much the same way one builds a Windows application linked against any
other MinGW DLL. In this case, using /usr/bin/i686-w64-mingw32-llvm-config in
the same way that pkg-config might be used for building against MinGW libraries
that include a .pc file.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
11 years, 11 months
non-static ".a" files? (mingw-pthreads)
by Eric Smith
If a mingw package build produces a ".a" file that is not usable as a
static library, is there any reason to include that ".a" file in the
package at all?
The specific case I'm wondering about is mingw-pthreads. I need a
static version, and mingw-pthreads needs special attention to build a
static version. The current package does include ".a" files in the
package, but they're definitely not static. Would it be appropriate to
just leave those out, and build actual static ".a" libraries to be put
into a "-static" subpackage?
Thanks!
Eric
11 years, 11 months
[Bug 819670] Review Request: mingw-llvm - MinGW LLVM libraries
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=819670
--- Comment #8 from Eric Smith <eric(a)brouhaha.com> 2012-05-12 18:42:37 EDT ---
The purpose of mingw-llvm is to be able to build applications for Windows that
use the LLVM libraries, e.g., if they want to use the LLVM JIT capabilities.
Such an app might possibly also be able to emit bitcode or even native code
files, though that isn't what I use it for personally.
The purpose of static libraries is to allow such programs to be built
statically, to avoid having to distribute them with a bunch of DLLs (including
but not limited to the LLVM DLLs). In other words, exactly the same reason as
for packaging any other mingnn-*-static subpackage.
I don't have any clue what an "llvm.exe" would do, even if it existed, which
AFAIK it doesn't. Certainly this package doesn't contain one.
The various .exe files that are in this package may or may not be useful to
people that use applications built with mingw-llvm, depending on exactly what
those applications do. I've had occasion to use a few of them. I could remove
them from the package, and only include the libraries, but I thought that as
long as the exe files were built and work, there was little advantage to not
packaging them.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
11 years, 11 months
[Bug 819670] Review Request: mingw-llvm - MinGW LLVM libraries
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=819670
Richard W.M. Jones <rjones(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rjones(a)redhat.com
--- Comment #7 from Richard W.M. Jones <rjones(a)redhat.com> 2012-05-12 18:26:56 EDT ---
As epienbro says, what's the point? There should perhaps be an llvm
cross-compiler, ie. a native llvm binary that can generate Windows
executables, but I don't see much point in an llvm.exe.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
11 years, 11 months
[Bug 819670] Review Request: mingw-llvm - MinGW LLVM libraries
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=819670
--- Comment #6 from Erik van Pienbroek <erik-fedora(a)vanpienbroek.nl> 2012-05-12 17:17:37 EDT ---
Perhaps I'm misunderstanding things, but what is the use case for this package?
Is llvm.exe and the other tools intended to be called using wine? How does one
get something linked against the LLVM-3.0.dll or is this only intended as
direct dependency of the llvm.exe and the other tools? What purpose do the
static libraries have?
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
11 years, 11 months