llvm-mingw | An LLVM/Clang/LLD based mingw-w64 toolchain | Compiler library

by mstorsjo C Version: 20230517 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | llvm-mingw Summary

llvm-mingw is a C library typically used in Utilities, Compiler applications. llvm-mingw has no bugs, it has no vulnerabilities and it has medium support. However llvm-mingw has a Non-SPDX License. You can download it from GitHub.

This is a recipe for reproducibly building a [LLVM] Clang(LLD(based mingw-w64 toolchain. Benefits of a LLVM based MinGW toolchain are: - Support for targeting ARM/ARM64 (while GCC obviously does support these architectures, it doesn’t support Windows on ARM) - A single toolchain targeting all four architectures (i686, x86_64, armv7 and arm64) instead of separate compiler binaries for each architecture - Support for generating debug info in PDB format - Support for Address Sanitizer and Undefined Behaviour Sanitizer. Clang on its own can also be used as compiler in the normal GNU binutils based environments though, so the main difference lies in replacing binutils with LLVM based tools.

Support

Quality

Security

License

Reuse

Support

llvm-mingw has a medium active ecosystem.

It has 1183 star(s) with 135 fork(s). There are 47 watchers for this library.

It had no major release in the last 12 months.

There are 53 open issues and 241 have been closed. On average issues are closed in 57 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of llvm-mingw is 20230517

Quality

llvm-mingw has 0 bugs and 0 code smells.

Security

llvm-mingw has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

llvm-mingw code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

llvm-mingw has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

llvm-mingw releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of llvm-mingw

Get all kandi verified functions for this library.

llvm-mingw Key Features

No Key Features are available at this moment for llvm-mingw.

llvm-mingw Examples and Code Snippets

No Code Snippets are available at this moment for llvm-mingw.

Community Discussions

Trending Discussions on llvm-mingw

How to add a custom library (e.g. glew) to mingw-w64?

Executing VLC for unity

Trying to build VLC for Unity3D

QUESTION

How to add a custom library (e.g. glew) to mingw-w64?

Asked 2021-Sep-13 at 13:01

I'm using windows and my goal is to add the glew library (http://glew.sourceforge.net/index.html) to mingw. I have downloaded mingw-w64 via GitHub (https://github.com/mstorsjo/llvm-mingw/releases/tag/20210423). It comes with a "bin", "lib" and "include" folder. Within the "bin" folder I do "make" to execute my project's makefile which inlcudes the line

...

ANSWER

Answered 2021-Sep-13 at 13:01

When using a library use the -I compiler flag to tell the compiler where to find the include files (in your case the path containing the GL folder) and the -L linker flag to tell the linker where to find the libraries.

To link with the library use the -l flag. The library itself is a a lib*.a file (or lib*.dll.a for shared libraries). For the -l flag the library is specified without prefix and suffix, so if your library is called libglew.a the flag will be -lglew.

It is also possible to specified the full path to the lib*.a file instead of -L and -l flags, and with MinGW, if you have the .dll file you can even try to specify the path of the .dll file and the linker will know what to do.

Source https://stackoverflow.com/questions/69136157

QUESTION

Executing VLC for unity

Asked 2020-Sep-15 at 07:19

I am facing similar issue like this mentioned in the post:

Triying to run VLC for unity plugin demo

Build platform is WIN 10 x64 (build 2004).

I am using LibVLC from the nightly build: https://artifacts.videolan.org/vlc/nightly-win64-llvm/20200914-0434/

LibVLCSharp gets built successfully (https://code.videolan.org/videolan/LibVLCSharp/-/tree/master/).

I was trying to build "VLCUnityPlugin.dll" but failing (have installed https://github.com/mstorsjo/llvm-mingw/tree/20200325 (LLVM MinGW)), using MSYS64 to run ./build.sh and it was coming up with this error:

MSYS error while building VLCUnity plugin dll

I thought maybe since "VLCUnityPlugin.dll" is NOT present, Unity x64 (v 2019.4.8f1) keeps on complaining with the following errors:

UNITY errors

But after, I hacked "common" make file as shown below:

make file changes to build VLCUnityPlugin.dll I successfully built VLCUnityPlugin.dll and my plugin file structure looks like this now: Plugin directory structure

Still, I do see UNITY Errors: "Assets\VLCUnity\Demos\Scripts\MinimalPlayback.cs(99,39): error CS1061: 'MediaPlayer' does not contain a definition for 'GetTexture' and no accessible extension method 'GetTexture' accepting a first argument of type 'MediaPlayer' could be found (are you missing a using directive or an assembly reference?)"

...

ANSWER

Answered 2020-Sep-15 at 07:19

The free trial version is available for download here https://videolabs.io/vlc-unity/vlc-unity-windows-trial.unitypackage.

That being said, if you want to build it yourself, you should follow what the CI does https://code.videolan.org/videolan/vlc-unity/-/blob/master/.gitlab-ci.yml

The libvlcsharp build is a special one, you need to define UNITY when you build it. It has the added GetTexture method.

For VLCPlugin.dll, you should crosscompile from Linux, where you install llvm-mingw and run it from bash (for example). MSYS not needed.

Source https://stackoverflow.com/questions/63892308

QUESTION

Trying to build VLC for Unity3D

Asked 2020-May-03 at 03:48

I have been trying to get the VLC plugin for Unity3D to build. It is found here: https://code.videolan.org/videolan/vlc-unity/blob/master/README.md

I am trying to do this on Debian 10 (buster).

The first instruction was to: Download and install https://github.com/mstorsjo/llvm-mingw on latest Debian (WSL or otherwise). Add it to path.

I believe I have done that part successfully.

Next is to: Download VLC nightly build and adjust if need be vlc-4.0.0-dev/sdk/lib path to LDFLAGS in Common.mk

This is where my issue is. I've done the snap install of the nightly build, I've downloaded the source with a -dev in name from here: https://nightlies.videolan.org/build/source/

I've also tried to use the master-daily PPA.

But I still cannot find any vlc-4.0.0-dev/sdk/lib path.

I have tried to set the LDFLAGS to some of the vlc lib folders I have, but every time I build I get this error:

...

ANSWER

Answered 2020-Feb-18 at 03:00

Since this plugin is currently Windows-only, I'm assuming you are targeting Windows.

Download a nightly from https://nightlies.videolan.org/build/win64-llvm/last/

You will find the libs at vlc-4.0.0-{date}-dev-win64.7z\vlc-4.0.0-dev\sdk\lib\

Source https://stackoverflow.com/questions/60216520

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install llvm-mingw

You can download it from GitHub.

Support

LLVM does [support](http://blog.llvm.org/2017/08/llvm-on-windows-now-supports-pdb-debug.html) generating debug info in the PDB format. Since GNU binutils based mingw environments don’t support this, there’s no predecent for what command line parameters to use for this, and llvm-mingw produces debug info in DWARF format by default.

Find more information at: