On 05/07/2012 11:19 PM, Eric Smith wrote:
> Now I get a .debuginfo package, but rpmlint reports that it doesn't
> actually contain sources. Any ideas on how to fix that?
That's expected for mingw packages, just ignore the rpmlint warning.
/usr/lib/rpm/mingw-find-debuginfo.sh doesn't have any code
Kalev Lember wrote:
Not sure, depends on if there are any apps would actually use it. It
might very well be that everything uses pkg-config .pc files instead
and the config script is just provided for backwards compatibility.
The llvm-config script does some fancy dependency analysis of the L
On 05/07/2012 09:22 PM, Eric Smith wrote:
> One more question has arisen. The LLVM build system installs an
> "llvm-config" Perl script, providing functionality specific to
> pkg-config, in %{mingw32_bindir}. If w64 builds were working, there
> would be a different one in %{mingw64_bindir}. Sinc
Kalev Lember wrote:
I have a vague recollection that llvm supports both autotools and
cmake builds systems. Perhaps another idea would be to use cmake, if
it's easier to cross compile llvm with it?
LLVM's cmake build system cannot produce the DLLs at all, so I'll stick
with the autotools.
On 05/07/2012 10:46 AM, Eric Smith wrote:
> I've finally found time to work on preparing a mingw-llvm-3.0 package,
> so that I can cross-compile a program that uses the LLVM libraries.
Hi Eric,
That's awesome, it'll be a very welcome addition to the mingw library
collection in Fedora.
> I've ru
I've finally found time to work on preparing a mingw-llvm-3.0 package,
so that I can cross-compile a program that uses the LLVM libraries.
I've run into a few problems that I could use some help with.
1) The %mingw_configure macro defines a bunch of environment variables
such as AR, CXX, GC
