# Limesuite NG installation instructions for Windows 11 - LimeSDR mini 2.0

**URL:** <https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566>\
**Category:** Lime Suite\
**Created:** [18 November 2024 18:43 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566 "2024-11-18T18:43:33Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [18 November 2024 18:43 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/1 "2024-11-18T18:43:34Z")

</div>

Hello,  
Please excuse me if this information is already available. I believe that I need to install limesuite NG for use of the LimeSDR mini 2.0 that I purchased from MOUSER. I have installed Limesuite, but that is not functional. It is not able to connect to the SDR. I had installed pothosware which was bundled with limesuite. Is there an updated bundle that has what is needed for the mini 2.0?  
I have been successful in installing and running GRC using LSDR mini 2.0 as a source for a simple RX experiment.

Thank you for any help on this.

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [19 November 2024 01:06 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/2 "2024-11-19T01:06:02Z")

</div>

I have now been able to connect to the LSDR mini 2.4 with the old Limesuite GUI in Windows 11. I installed the “PothosSDR-2021.07.25-vc16-x64” for Pothos FLow and Cubic-SDR, and radioconda-2024.05.29-Windows-x86\_64 to get GRC.

The configurability is excellent with the LimeSuite GUI, but now I am needing to work through how to configure the LimeSDR while using it in the context of GRC or Pothos Flow.

I only see Soapy LimeSDR Sources/Sinks available in GRC, and I haven’t tried it in Pothos Flow yet. I do have some simple RX cases working in GRC.

So here’s a question: how can I configure the Lime SDR mini 2.x device to a high degree (As the Lime Suit GUI enables) while using it inside GRC? Is this possible?

One strange thing I noticed is that when I run CubicSDR, I only see reception when selecting the LNAH Antenna option. I don’t see any signals when LNAL, LNAW, and of course NONE is selected. Is this a bug with CubicSDR, a driver issue, or what.

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [19 November 2024 12:46 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/3 "2024-11-19T12:46:10Z")

</div>

> [@ngriesert](#):
>
> I believe that I need to install limesuite NG for use of the LimeSDR mini 2.0

LimeSDR mini v2 is supported by both LimeSuiteNG, and legacy LimeSuite(v22.09 and up, older versions can see v2, but uses it as v1 so it won’t work correctly).  
LimeSuiteNG should be preferred, but currently main development is focused on Linux, so packaging for Windows is not ready yet.

> [@ngriesert](#):
>
> So here’s a question: how can I configure the Lime SDR mini 2.x device to a high degree (As the Lime Suit GUI enables) while using it inside GRC? Is this possible?

It’s possible by saving your configuration from the GUI into .ini file. And then specifying that file to be loaded by GRC block, file will be used as base configuration, and GRC will overwrite the generic SDR parameters (LO, bandwidth, sample rate…)

> [@ngriesert](#):
>
> One strange thing I noticed is that when I run CubicSDR, I only see reception when selecting the LNAH Antenna option. I don’t see any signals when LNAL,

If I remember correctly, CubicSDR uses statically linked LimeSuite library, so it might be that at the time CubicSDR was compiled, that LimeSuite version did not had support for LimeSDR mini v2, so as I mentioned earlier it uses it as v1 and might not work correctly (the RF switches contolling which antenna to use are in different registers on v1 and v2, so that could be reason why the default LNAH works, but won’t switch to LNAW). On LimeSDR mini v2 the LNAL is not physically connected to antenna port, so it is expected to not work.

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [19 November 2024 18:16 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/4 "2024-11-19T18:16:34Z")

</div>

Thank you for the helpful feedback!

The version of LimeSuite that I think I have (copied out of the PowerShell) is:

######################################################

## LimeSuite information summary

######################################################  
Version information:  
Library version: v20.10.0-PothosSDR-2021.07.25-vc16-x64  
Build timestamp: 2021-07-25  
Interface version: v2020.10.0  
Binary interface: 20.10-1

So it sounds like it’s a surprise that I’m having any success connecting to the mini 2.0? Is that right? Does it make sense that I am able to communicate with the device at all? Is there a more recent version available to install in Windows that I can access? I am inexperienced building software packages (I’m not sure I’m even saying that right), but if that’s what I need to do I’ll learn it. It’s always helpful to have examples to follow when getting started.

Generally, I am really impressed with the Lime SDR hardware. It looks very attractive when comparing to some other SDR RX/TX options out there. I want to figure out how to make it work for my needs. It seems that documentation for the mini 2.0 is nested here and there, or not posted (I have no doubt it exists somewhere). Also finding software as a Windows user is not going well. I want to be able to have students work with this hardware in some undergraduate university courses, and I want them to be able to load software onto their own laptops. Even if I get a linux box it doesn’t solve that issue, as far as I can tell.

Is there any development for Windows on the horizon, or is that just not worth the development folks’ time with all that’s going on?

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [19 November 2024 18:39 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/5 "2024-11-19T18:39:18Z")

</div>

I had also checked here:

> **[GitHub - myriadrf/LimeSuiteNG](https://github.com/myriadrf/LimeSuiteNG)**
>
> Contribute to myriadrf/LimeSuiteNG development by creating an account on GitHub.

to see if I could do a windows install. There are some directions on how to do this that say:

### Windows:

```auto
git clone https://github.com/myriadrf/LimeSuiteNG
cd LimeSuiteNG
cmake -B build
cmake --build build

```

I installed cmake on my windows machine and tried that with poor results. It didn’t work. Is there an option for Windows?

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [19 November 2024 18:56 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/6 "2024-11-19T18:56:36Z")

</div>

> [@ngriesert](#):
>
> So it sounds like it’s a surprise that I’m having any success connecting to the mini 2.0? Is that right? Does it make sense that I am able to communicate with the device at all?

It has the same USB controller, and the communications protocol is the same, so it just works, but that software version does not know about the FPGA register addresses changes.

> [@ngriesert](#):
>
> Is there any development for Windows on the horizon, or is that just not worth the development folks’ time with all that’s going on?

There is, the LimeSuiteNG already works on Windows, the only exception so far is that PCIe devices driver is not available. Everything with USB is working.  
Windows as a platform main problem is discovering where all other software packages are installed or located. So it’s more complicated to automate building plugins for other software packages, because all the paths where they could be found on the system have to be set manually.

> [@ngriesert](#):
>
> I installed cmake on my windows machine and tried that with poor results. It didn’t work. Is there an option for Windows?

Those instructions should be enough to build the main LimeSuiteNG components, all dependencies are downloaded automatically. What problems are you experiencing? Do you have Microsoft Visual C++ compiler installed on your system, or are you using some other compiler?

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [19 November 2024 19:35 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/7 "2024-11-19T19:35:28Z")

</div>

Ok, I had installed visual studio 2022. I had assumed that it included the needed compilers, but maybe that was a bad assumption.

Here is an image showing an error when I try to run the limeGUI:

 ![image](https://canada1.discourse-cdn.com/flex034/uploads/myriadrf/original/2X/9/96a3c9edff512863aa8f7dd0a91f4674ce10dd75.png)

I don’t know where the dll is. I just followed the directions 🙂

General note: I have installed a number of drivers and software to get the SDR Rxs and the Limesdr to function. I have a functional pothos flow that is very old and I’m not sure how useful with the Lime SDR, then I have a gnu radio companion installation that’s working, but only has the simple SoapyLime Sources, and now I’m trying to upgrade the LimeSDR interfacing software. Do I need to be concerned about creating conflicts amongst these installs?

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [19 November 2024 19:43 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/8 "2024-11-19T19:43:56Z")

</div>

When these builds and installs are getting done, are configuration files or paths being written outside the directory structures where I am doing the install? I guess, what I’m wanting to know is in the case where there is no “uninstall” script, can I simply wipe out the whole directory structure of what had been installed and start over if needed?

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [19 November 2024 19:45 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/9 "2024-11-19T19:45:01Z")

</div>

Where is a preferred location to carry out the build? Somewhere under the /Program Files folder, or is somewhere under /Users/me/ any better?

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [19 November 2024 20:38 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/10 "2024-11-19T20:38:10Z")

</div>

> [@ngriesert](#):
>
> General note: I have installed a number of drivers and software to get the SDR Rxs and the Limesdr to function. I have a functional pothos flow that is very old and I’m not sure how useful with the Lime SDR, then I have a gnu radio companion installation that’s working, but only has the simple SoapyLime Sources, and now I’m trying to upgrade the LimeSDR interfacing software. Do I need to be concerned about creating conflicts amongst these installs?

LimeSuiteNG is not affected by other software, so everything should be fine.  
The only current conflict could be LimeSuiteNG overriding legacy LimeSuite “gr-limesdr” GNURadio plugin, GRC LimeSDR-sink/source blocks that previously were running LimeSuite would start using LimeSuiteNG.

> [@ngriesert](#):
>
> When these builds and installs are getting done, are configuration files or paths being written outside the directory structures where I am doing the install?

When just building the project, everything is contained inside the LimeSuiteNG/build directory, if you want to do fresh rebuild, delete ‘build’ directory and repeat build instructions.

Installation step copies files from build into system directories.  
By default everything is installed into “C:/Program Files (x86)/LimeSuiteNG/”  
Or you can specify your own install directory by adding cmake argument  
`cmake -B build -DCMAKE_INSTALL_PREFIX=yourPath`  
The install/uninstall procedure on Windows is not thoroughly tested, so might have issues.  
\*The installation command has to be ran as Administrator, otherwise installation will fail, as it won’t have privileges to create subdirectories inside “Program Files”.

To install on Windows:  
`cmake --build build --target install --config Release`  
To uninstall:  
`cmake --build build --target uninstall --config Release`

I’ve tried on Windows, the LimeSuiteNG files are correctly installed to “Program Files”, but the path is not added to windows environment variables where to look for binaries.

Because there is no official GNURadio installer for windows, LimeSuiteNG won’t automatically find where it is installed, it needs to be specified for the cmake with ‘-DGnuradio\_DIR=path’

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [19 November 2024 20:43 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/11 "2024-11-19T20:43:56Z")

</div>

> [@ngriesert](#):
>
> Where is a preferred location to carry out the build? Somewhere under the /Program Files folder, or is somewhere under /Users/me/ any better?

The build step can be done anywhere, as it’s a intermediate step, so usually it’s inside the project’s source directory, that “build” folder that you create.

The “install” step then copies files from build into where they are designated to be on the system.

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [19 November 2024 21:57 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/12 "2024-11-19T21:57:19Z")

</div>

Thank you very much!

One clarifying question here:  
You said:

“Because there is no official GNURadio installer for windows, LimeSuiteNG won’t automatically find where it is installed, it needs to be specified for the cmake with ‘-DGnuradio\_DIR=path’”.

Are you saying that when I install I need to do something like:

cmake -DGnuradio\_DIR=my\_path  
cmake --build build --target install --config Release

to specify the path for the install?

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [19 November 2024 23:03 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/13 "2024-11-19T23:03:48Z")

</div>

For LimeSuiteNG the -DGnuradioDIR=path defines the root directory of GNURadio, which is then used as entry point to find the necessary libraries within that are required for building a GRC plugin. It also acts as entry point to find directories where to install the created plugin.

In any case, it gets quite complicated on Windows to gather/specify where everything is located. In case of GNURadio installed through Conda, you additionally have to manage the Conda environment: [CondaInstall - GNU Radio](https://wiki.gnuradio.org/index.php/CondaInstall#Building_OOT_modules_to_use_with_conda-installed_GNU_Radio)

What I’m trying to say is that it’s possible to get everything working on Windows now, but at this stage, integrating into other software is quite complicated and requires manual effort. I do intend to improve that, but I can’t give you an estimate when that will be done.

Simplest option to start using LimeSuiteNG with GNURadio would be to use Linux system, it’s standardized so most things are automated.

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [19 November 2024 23:22 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/14 "2024-11-19T23:22:33Z")

</div>

Build Log

PS C:\Users\ngriesert\source\LimeSuiteNG\> C:"Program Files"\CMake\bin\cmake -B build  
– Building for: Visual Studio 17 2022  
– cmake version: 3.31.0  
– Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.26100.  
– The C compiler identification is MSVC 19.41.34120.0  
– The CXX compiler identification is MSVC 19.41.34120.0  
– Detecting C compiler ABI info  
– Detecting C compiler ABI info - done  
– Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.41.34120/bin/Hostx64/x64/cl.exe - skipped  
– Detecting C compile features  
– Detecting C compile features - done  
– Detecting CXX compiler ABI info  
– Detecting CXX compiler ABI info - done  
– Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.41.34120/bin/Hostx64/x64/cl.exe - skipped  
– Detecting CXX compile features  
– Detecting CXX compile features - done  
CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:1373 (message):  
The DOWNLOAD\_EXTRACT\_TIMESTAMP option was not given and policy CMP0135 is  
not set. The policy’s OLD behavior will be used. When using a URL  
download, the timestamps of extracted files should preferably be that of  
the time of extraction, otherwise code that depends on the extracted  
contents might not be rebuilt if the URL changes. The OLD behavior  
preserves the timestamps from the archive instead, but this is usually not  
what you want. Update your project to the NEW behavior or specify the  
DOWNLOAD\_EXTRACT\_TIMESTAMP option with a value of true to avoid this  
robustness issue.  
Call Stack (most recent call first):  
external/CMakeLists.txt:11 (fetchcontent\_declare)  
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:1564 (cmake\_parse\_arguments):  
The BUILD\_COMMAND keyword was followed by an empty string or no value at  
all. Policy CMP0174 is not set, so cmake\_parse\_arguments() will unset the  
ARG\_BUILD\_COMMAND variable rather than setting it to an empty string.  
Call Stack (most recent call first):  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145:EVAL:2 (\_\_FetchContent\_doPopulation)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145 (cmake\_language)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2384 (\_\_FetchContent\_Populate)  
external/CMakeLists.txt:16 (fetchcontent\_makeavailable)  
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:1564 (cmake\_parse\_arguments):  
The CONFIGURE\_COMMAND keyword was followed by an empty string or no value  
at all. Policy CMP0174 is not set, so cmake\_parse\_arguments() will unset  
the ARG\_CONFIGURE\_COMMAND variable rather than setting it to an empty  
string.  
Call Stack (most recent call first):  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145:EVAL:2 (\_\_FetchContent\_doPopulation)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145 (cmake\_language)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2384 (\_\_FetchContent\_Populate)  
external/CMakeLists.txt:16 (fetchcontent\_makeavailable)  
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:1953 (message):  
Calling FetchContent\_Populate(kissFFT) is deprecated, call  
FetchContent\_MakeAvailable(kissFFT) instead. Policy CMP0169 can be set to  
OLD to allow FetchContent\_Populate(kissFFT) to be called directly for now,  
but the ability to call it with declared details will be removed completely  
in a future version.  
Call Stack (most recent call first):  
external/CMakeLists.txt:67 (fetchcontent\_populate)  
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Deprecation Warning at build/\_deps/kissfft-src/CMakeLists.txt:35 (cmake\_minimum\_required):  
Compatibility with CMake \< 3.10 will be removed from a future version of  
CMake.

Update the VERSION argument value or use a … suffix to tell  
CMake that the project does not need compatibility with older versions.

– Building KissFFT with datatype: float  
– Building static library  
– PKGINCLUDEDIR is /kissfft  
CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:1953 (message):  
Calling FetchContent\_Populate(args) is deprecated, call  
FetchContent\_MakeAvailable(args) instead. Policy CMP0169 can be set to OLD  
to allow FetchContent\_Populate(args) to be called directly for now, but the  
ability to call it with declared details will be removed completely in a  
future version.  
Call Stack (most recent call first):  
external/CMakeLists.txt:103 (fetchcontent\_populate)  
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Deprecation Warning at build/\_deps/args-src/CMakeLists.txt:22 (cmake\_minimum\_required):  
Compatibility with CMake \< 3.10 will be removed from a future version of  
CMake.

Update the VERSION argument value or use a … suffix to tell  
CMake that the project does not need compatibility with older versions.

CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:1564 (cmake\_parse\_arguments):  
The BUILD\_COMMAND keyword was followed by an empty string or no value at  
all. Policy CMP0174 is not set, so cmake\_parse\_arguments() will unset the  
ARG\_BUILD\_COMMAND variable rather than setting it to an empty string.  
Call Stack (most recent call first):  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145:EVAL:2 (\_\_FetchContent\_doPopulation)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145 (cmake\_language)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2384 (\_\_FetchContent\_Populate)  
external/CMakeLists.txt:116 (fetchcontent\_makeavailable)  
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:1564 (cmake\_parse\_arguments):  
The CONFIGURE\_COMMAND keyword was followed by an empty string or no value  
at all. Policy CMP0174 is not set, so cmake\_parse\_arguments() will unset  
the ARG\_CONFIGURE\_COMMAND variable rather than setting it to an empty  
string.  
Call Stack (most recent call first):  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145:EVAL:2 (\_\_FetchContent\_doPopulation)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145 (cmake\_language)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2384 (\_\_FetchContent\_Populate)  
external/CMakeLists.txt:116 (fetchcontent\_makeavailable)  
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:1564 (cmake\_parse\_arguments):  
The BUILD\_COMMAND keyword was followed by an empty string or no value at  
all. Policy CMP0174 is not set, so cmake\_parse\_arguments() will unset the  
ARG\_BUILD\_COMMAND variable rather than setting it to an empty string.  
Call Stack (most recent call first):  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145:EVAL:2 (\_\_FetchContent\_doPopulation)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145 (cmake\_language)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2384 (\_\_FetchContent\_Populate)  
external/CMakeLists.txt:131 (fetchcontent\_makeavailable)  
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Warning (dev) at C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:1564 (cmake\_parse\_arguments):  
The CONFIGURE\_COMMAND keyword was followed by an empty string or no value  
at all. Policy CMP0174 is not set, so cmake\_parse\_arguments() will unset  
the ARG\_CONFIGURE\_COMMAND variable rather than setting it to an empty  
string.  
Call Stack (most recent call first):  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145:EVAL:2 (\_\_FetchContent\_doPopulation)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2145 (cmake\_language)  
C:/Program Files/CMake/share/cmake-3.31/Modules/FetchContent.cmake:2384 (\_\_FetchContent\_Populate)  
external/CMakeLists.txt:131 (fetchcontent\_makeavailable)  
This warning is for project developers. Use -Wno-dev to suppress it.

CMake Deprecation Warning at build/\_deps/rang-src/CMakeLists.txt:1 (cmake\_minimum\_required):  
Compatibility with CMake \< 3.10 will be removed from a future version of  
CMake.

Update the VERSION argument value or use a … suffix to tell  
CMake that the project does not need compatibility with older versions.

– Performing Test CMAKE\_HAVE\_LIBC\_PTHREAD  
– Performing Test CMAKE\_HAVE\_LIBC\_PTHREAD - Failed  
– Looking for pthread\_create in pthreads  
– Looking for pthread\_create in pthreads - not found  
– Looking for pthread\_create in pthread  
– Looking for pthread\_create in pthread - not found  
– Found Threads: TRUE  
– FTDI\_INCLUDE\_DIRS: C:/Users/ngriesert/source/LimeSuiteNG/external/FTD3XXLibrary  
– FTDI\_LIBRARIES: C:/Users/ngriesert/source/LimeSuiteNG/external/FTD3XXLibrary/x64/Static\_Lib/FTD3XX.lib;SetupAPI  
– Cypress backend not available. The following location does not exist: FX3\_SDK\_PATH=  
– Downloading FX3SDK to: C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/fx3sdk  
– CyAPI includes: C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/fx3sdk/library/cpp/inc  
– CyAPI libs: C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/fx3sdk/library/cpp/lib/x64/CyAPI.lib;SetupAPI.lib  
– Could NOT find wxWidgets (missing: wxWidgets\_LIBRARIES wxWidgets\_INCLUDE\_DIRS richtext adv core base gl)  
– Downloading wxWidgets headers.  
– Found wxWidgets: debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32ud\_richtext.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32u\_richtext.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32ud\_adv.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32u\_adv.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32ud\_core.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32u\_core.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxbase32ud.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxbase32u.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32ud\_gl.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32u\_gl.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxpngd.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxpng.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxtiffd.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxtiff.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxjpegd.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxjpeg.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxzlibd.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxzlib.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxregexud.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxregexu.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxexpatd.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxexpat.lib;opengl32;glu32;gdiplus;msimg32;winmm;comctl32;uuid;oleacc;uxtheme;rpcrt4;shlwapi;version;wsock32 (found version “3.2.5”) found components: richtext adv core base gl png tiff jpeg zlib regex expat  
– wxWidgets\_DEFINITIONS: WXUSINGDLL;UNICODE;\_UNICODE  
– wxWidgets\_INCLUDE\_DIRS: C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/mswu;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/include  
– wxWidgets\_LIBRARIES: debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32ud\_richtext.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32u\_richtext.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32ud\_adv.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32u\_adv.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32ud\_core.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32u\_core.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxbase32ud.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxbase32u.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32ud\_gl.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxmsw32u\_gl.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxpngd.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxpng.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxtiffd.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxtiff.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxjpegd.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxjpeg.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxzlibd.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxzlib.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxregexud.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxregexu.lib;debug;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxexpatd.lib;optimized;C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/wxWidgets/lib/vc14x\_x64\_dll/wxexpat.lib;opengl32;glu32;gdiplus;msimg32;winmm;comctl32;uuid;oleacc;uxtheme;rpcrt4;shlwapi;version;wsock32  
– Found OpenGL: opengl32  
– OPENGL\_INCLUDE\_DIR:  
– OPENGL\_LIBRARIES: opengl32;glu32  
CMake Deprecation Warning at plugins/amarisoft-plugin/CMakeLists.txt:1 (cmake\_minimum\_required):  
Compatibility with CMake \< 3.10 will be removed from a future version of  
CMake.

Update the VERSION argument value or use a … suffix to tell  
CMake that the project does not need compatibility with older versions.

## – Could NOT find SoapySDR (missing: SoapySDR\_DIR) – Could NOT find Doxygen (missing: DOXYGEN\_EXECUTABLE)

– ######################################################  
– Packages found:

- Threads
- CyAPI  
Adds USB communication support for Cypress FX3 chip
- wxWidgets
- OpenGL

– ######################################################  
– Missing required packages:

– ######################################################  
– Missing recommended packages:

– ######################################################  
– Missing optional packages:

- SoapySDR  
Adds LimeSuiteNG bindings for SoapySDR
- Doxygen

## – ###################################################### – ## LimeSuiteNG enabled features – ######################################################

- HEADERS, The limesuiteng headers
- LIBRARY, The limesuiteng library
- USB\_FTDI, USB support for FTDI
- USB\_FX3, USB support for Cypress FX3
- EXAMPLES, LimeSuite library API examples
- CLI, LimeSuite command line interface tools
- GUI, GUI Application for LimeSuite

## – ###################################################### – ## LimeSuiteNG disabled features – ######################################################

- SOAPYSDR, SoapySDR bindings for LimeSuiteNG
- GNURADIO, GNU Radio 3.9+ Plug-in
- HDSDR, HDSDR (32bit only) plugin for limesuiteng
- DOXYGEN, Build Doxygen documentation

– Install prefix: C:/Program Files (x86)/LimeSuiteNG  
– Build timestamp: 2024-11-19  
– Lime Suite version: 0.2.0-gd0df4d0c  
– ABI/so version: 0.2-1  
– Configuring done (54.0s)  
– Generating done (1.3s)  
– Build files have been written to: C:/Users/ngriesert/source/LimeSuiteNG/build  
PS C:\Users\ngriesert\source\LimeSuiteNG\>

* * *

## XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [19 November 2024 23:55 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/15 "2024-11-19T23:55:39Z")

</div>

Install Log:

PS C:\Users\ngriesert\source\LimeSuiteNG\> C:"Program Files"\CMake\bin\cmake --build build --target install --config Release  
MSBuild version 17.11.9+a69bbaaf5 for .NET Framework

1\>Checking Build System  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/embedded/gfir/CMakeLists.txt  
corrections.c  
gfir\_lms.c  
lms.c  
recipes.c  
rounding.c  
lms\_gfir.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\embedded\gfir\lms\_gfir.dir\Release\lms\_gfir.lib  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/build/\_deps/kissfft-src/CMakeLists.txt  
kiss\_fft.c  
kfc.c  
kiss\_fftnd.c  
kiss\_fftndr.c  
kiss\_fftr.c  
kissfft.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\_deps\kissfft-build\Release\kissfft-float.lib  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/embedded/lms7002m/CMakeLists.txt  
lms7002m.c  
calibrations.c  
privates.c  
save\_state.c  
spi.c  
lms7002m.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\embedded\lms7002m\Release\lms7002m.lib  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/src/CMakeLists.txt  
StreamComposite.cpp  
CommonFunctions.cpp  
OEMTesting.cpp  
Logger.cpp  
LoggerCString.cpp  
LMS64CProtocol.cpp  
LMSBoards.cpp  
FPGA\_common.cpp  
WriteRegistersBatch.cpp  
threadHelper.cpp  
MemoryPool.cpp  
LMS\_APIWrapper.cpp  
LimePlugin.cpp  
SDRDevice.cpp  
toString.cpp  
VersionInfo.cpp  
SystemResources.cpp  
FT601.cpp  
FX3.cpp  
LMS64C\_FPGA\_Over\_USB.cpp  
LMS64C\_LMS7002M\_Over\_USB.cpp  
LMS64C\_ADF4002\_Over\_USB.cpp  
USBDMAEmulation.cpp  
SPIChipSelectShim.cpp  
SPI\_utilities.cpp  
DeviceRegistry.cpp  
DeviceHandle.cpp  
LMS7002M\_SDRDevice.cpp  
LimeSDR.cpp  
USB\_CSR\_Pipe\_SDR.cpp  
DeviceFactoryFX3.cpp  
LimeSDR\_Mini.cpp  
FPGA\_Mini.cpp  
USB\_CSR\_Pipe\_Mini.cpp  
LimeNET\_Micro.cpp  
DeviceFactoryFTDI.cpp  
ADF4002.cpp  
CDCM6208.cpp  
LMS7002M\_RegistersMap.cpp  
LMS7002M.cpp  
LMS7002MCSR\_Data.cpp  
LMS7002MCSR\_To\_LMS7002MCSR\_Data.cpp  
validation.cpp  
filtersCalibration.cpp  
gainCalibrations.cpp  
mcu\_dc\_iq\_calibration.cpp  
MCU\_BD.cpp  
MCU\_File.cpp  
Si5351C.cpp  
CrestFactorReduction.cpp  
FFT.cpp  
samplesConversion.cpp  
TRXLooper.cpp  
BufferInterleaving.cpp  
AvgRmsCounter.cpp  
BoardSupportLoader.cpp  
C:\Users\ngriesert\source\LimeSuiteNG\src\boards\LimeSDR\_Mini\LimeNET\_Micro.cpp(461,28): warning C4477: ‘sscanf’ : form  
at string ‘%16lX’ requires an argument of type ‘unsigned long \*’, but variadic argument 1 has type ‘uint64\_t \*’ [C:\Use  
rs\ngriesert\source\LimeSuiteNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\boards\LimeSDR\_Mini\LimeNET\_Micro.cpp(461,28):  
consider using ‘%llX’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\boards\LimeSDR\_Mini\LimeNET\_Micro.cpp(461,28):  
consider using ‘%IX’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\boards\LimeSDR\_Mini\LimeNET\_Micro.cpp(461,28):  
consider using ‘%I64X’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(232,45): warning C4477: ‘snprintf’ : format string ‘%  
li’ requires an argument of type ‘long’, but variadic argument 2 has type ‘int64\_t’ [C:\Users\ngriesert\source\LimeSuit  
eNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(232,45):  
consider using ‘%lli’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(232,45):  
consider using ‘%Ii’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(232,45):  
consider using ‘%I64i’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17): warning C4477: ‘snprintf’ : format string ‘%  
li’ requires an argument of type ‘long’, but variadic argument 2 has type ‘int64\_t’ [C:\Users\ngriesert\source\LimeSuit  
eNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17):  
consider using ‘%lli’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17):  
consider using ‘%Ii’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17):  
consider using ‘%I64i’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17): warning C4477: ‘snprintf’ : format string ‘%  
08lX’ requires an argument of type ‘unsigned long’, but variadic argument 3 has type ‘int64\_t’ [C:\Users\ngriesert\sour  
ce\LimeSuiteNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17):  
consider using ‘%llX’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17):  
consider using ‘%IX’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17):  
consider using ‘%I64X’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17): warning C4477: ‘snprintf’ : format string ‘%  
li’ requires an argument of type ‘long’, but variadic argument 6 has type ‘int64\_t’ [C:\Users\ngriesert\source\LimeSuit  
eNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17):  
consider using ‘%lli’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17):  
consider using ‘%Ii’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(257,17):  
consider using ‘%I64i’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17): warning C4477: ‘snprintf’ : format string ‘%  
li’ requires an argument of type ‘long’, but variadic argument 4 has type ‘uint64\_t’ [C:\Users\ngriesert\source\LimeSui  
teNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%lli’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%Ii’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%I64i’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17): warning C4477: ‘snprintf’ : format string ‘%  
li’ requires an argument of type ‘long’, but variadic argument 5 has type ‘int64\_t’ [C:\Users\ngriesert\source\LimeSuit  
eNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%lli’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%Ii’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%I64i’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17): warning C4477: ‘snprintf’ : format string ‘%  
lu’ requires an argument of type ‘unsigned long’, but variadic argument 10 has type ‘uint64\_t’ [C:\Users\ngriesert\sour  
ce\LimeSuiteNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%llu’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%Iu’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%I64u’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17): warning C4477: ‘snprintf’ : format string ‘%  
lu’ requires an argument of type ‘unsigned long’, but variadic argument 11 has type ‘uint64\_t’ [C:\Users\ngriesert\sour  
ce\LimeSuiteNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%llu’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%Iu’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%I64u’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17): warning C4477: ‘snprintf’ : format string ‘%  
li’ requires an argument of type ‘long’, but variadic argument 12 has type ‘uint64\_t’ [C:\Users\ngriesert\source\LimeSu  
iteNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%lli’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%Ii’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%I64i’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17): warning C4477: ‘snprintf’ : format string ‘%  
li’ requires an argument of type ‘long’, but variadic argument 13 has type ‘size\_t’ [C:\Users\ngriesert\source\LimeSuit  
eNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(547,17):  
consider using ‘%zi’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\boards\LimeSDR\_Mini\LimeSDR\_Mini.cpp(553,28): warning C4477: ‘sscanf’ : forma  
t string ‘%16lX’ requires an argument of type ‘unsigned long \*’, but variadic argument 1 has type ‘uint64\_t \*’ [C:\User  
s\ngriesert\source\LimeSuiteNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\boards\LimeSDR\_Mini\LimeSDR\_Mini.cpp(553,28):  
consider using ‘%llX’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\boards\LimeSDR\_Mini\LimeSDR\_Mini.cpp(553,28):  
consider using ‘%IX’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\boards\LimeSDR\_Mini\LimeSDR\_Mini.cpp(553,28):  
consider using ‘%I64X’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21): warning C4477: ‘snprintf’ : format string ’  
%li’ requires an argument of type ‘long’, but variadic argument 4 has type ‘int64\_t’ [C:\Users\ngriesert\source\LimeSui  
teNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%lli’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%Ii’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%I64i’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21): warning C4477: ‘snprintf’ : format string ’  
%li’ requires an argument of type ‘long’, but variadic argument 5 has type ‘int64\_t’ [C:\Users\ngriesert\source\LimeSui  
teNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%lli’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%Ii’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%I64i’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21): warning C4477: ‘snprintf’ : format string ’  
%lu’ requires an argument of type ‘unsigned long’, but variadic argument 10 has type ‘uint64\_t’ [C:\Users\ngriesert\sou  
rce\LimeSuiteNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%llu’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%Iu’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%I64u’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21): warning C4477: ‘snprintf’ : format string ’  
%lu’ requires an argument of type ‘unsigned long’, but variadic argument 11 has type ‘uint64\_t’ [C:\Users\ngriesert\sou  
rce\LimeSuiteNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%llu’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%Iu’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%I64u’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21): warning C4477: ‘snprintf’ : format string ’  
%+li’ requires an argument of type ‘long’, but variadic argument 12 has type ‘uint64\_t’ [C:\Users\ngriesert\source\Lime  
SuiteNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%lli’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%Ii’ in the format string  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%I64i’ in the format string

C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21): warning C4477: ‘snprintf’ : format string ’  
%li’ requires an argument of type ‘long’, but variadic argument 17 has type ‘size\_t’ [C:\Users\ngriesert\source\LimeSui  
teNG\build\src\limesuiteng.vcxproj]  
C:\Users\ngriesert\source\LimeSuiteNG\src\streaming\TRXLooper.cpp(1011,21):  
consider using ‘%zi’ in the format string

```
 Creating library C:/Users/ngriesert/source/LimeSuiteNG/build/src/Release/limesuiteng.lib and object C:/Users/ngrie

```

sert/source/LimeSuiteNG/build/src/Release/limesuiteng.exp  
LINK : warning LNK4098: defaultlib ‘LIBCMT’ conflicts with use of other libs; use /NODEFAULTLIB:library [C:\Users\ngrie  
sert\source\LimeSuiteNG\build\src\limesuiteng.vcxproj]  
limesuiteng.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\src\Release\limesuiteng.dll  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/cli/CMakeLists.txt  
cmake\_pch.cxx  
common.cpp  
cli-shared.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\cli\Release\cli-shared.lib  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/src/examples/CMakeLists.txt  
basicRX.cpp  
basicRX.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\examples\Release\basicRX.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/src/examples/CMakeLists.txt  
basicTX.cpp  
basicTX.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\examples\Release\basicTX.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/src/examples/CMakeLists.txt  
dualRXTX.cpp  
dualRXTX.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\examples\Release\dualRXTX.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/src/examples/CMakeLists.txt  
basicRX.cpp  
legacyBasicRX.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\examples\legacy\Release\basicRX.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/src/examples/CMakeLists.txt  
basicTX.cpp  
legacyBasicTX.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\examples\legacy\Release\basicTX.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/src/examples/CMakeLists.txt  
dualRXTX.cpp  
legacyDualRXTX.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\examples\legacy\Release\dualRXTX.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/src/examples/CMakeLists.txt  
gpio\_example.cpp  
legacyGpio\_example.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\examples\legacy\Release\gpio\_example.ex  
e  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/src/examples/CMakeLists.txt  
singleRX.cpp  
legacySingleRX.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\examples\legacy\Release\singleRX.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/cli/CMakeLists.txt  
limeConfig.cpp  
limeConfig.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\Release\limeConfig.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/cli/CMakeLists.txt  
limeDevice.cpp  
limeDevice.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\Release\limeDevice.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/cli/CMakeLists.txt  
limeFLASH.cpp  
limeFLASH.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\Release\limeFLASH.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/external/CMakeLists.txt  
glew.c  
GLEW.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\external\Release\GLEW.lib  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/GUI/CMakeLists.txt  
cmake\_pch.cxx  
limeGUI.cpp  
limeGUIFrame.cpp  
LMS\_Programming\_wxgui.cpp  
pnlMiniLog.cpp  
SPI\_wxgui.cpp  
dlgFullMessageLog.cpp  
utilities\_gui.cpp  
dlgAbout\_view.cpp  
dlgAbout.cpp  
numericSlider.cpp  
fftviewer\_wxgui.cpp  
fftviewer\_frFFTviewer.cpp  
CommsToDevice.cpp  
DeviceConnectionPanel.cpp  
events.cpp  
SDRConfiguration\_view.cpp  
CoefficientFileParser.cpp  
pnlBoardControls.cpp  
pnlBuffers.cpp  
pnlGPIO.cpp  
pnlX3.cpp  
pnlX8.cpp  
pnlXTRX.cpp  
pnluLimeSDR.cpp  
pnlLimeSDR.cpp  
ADF4002\_wxgui.cpp  
CDCM6208\_wxgui.cpp  
Si5351C\_wxgui.cpp  
ILMS7002MTab.cpp  
lms7002\_pnlXBUF\_view.cpp  
lms7002\_pnlRFE\_view.cpp  
lms7002\_pnlCalibrations\_view.cpp  
lms7002\_pnlTRF\_view.cpp  
lms7002\_pnlCDS\_view.cpp  
lms7002\_pnlLimeLightPAD\_view.cpp  
lms7002\_pnlBIST\_view.cpp  
dlgViewIRAM.cpp  
lms7002\_gui\_utilities.cpp  
lms7002\_pnlSX\_view.cpp  
lms7002\_pnlTBB\_view.cpp  
lms7002\_pnlRBB\_view.cpp  
lms7002\_pnlLDO\_view.cpp  
lms7002\_pnlAFE\_view.cpp  
lms7002\_pnlGains\_view.cpp  
lms7002\_pnlRxTSP\_view.cpp  
lms7002\_mainPanel.cpp  
lms7002\_pnlCLKGEN\_view.cpp  
lms7002\_pnlMCU\_BD\_view.cpp  
lms7002\_pnlBIAS\_view.cpp  
lms7002\_dlgGFIR\_Coefficients.cpp  
lms7002\_pnlTxTSP\_view.cpp  
lms7002\_pnlR3.cpp  
dlgMarkers.cpp  
GLFont.cpp  
OpenGLGraph.cpp  
limeGUI.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\Release\limeGUI.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/cli/CMakeLists.txt  
limeOEM.cpp  
limeOEM.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\Release\limeOEM.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/cli/CMakeLists.txt  
limeSPI.cpp  
limeSPI.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\Release\limeSPI.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/cli/CMakeLists.txt  
limeTRX.cpp  
limeTRX.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\bin\Release\limeTRX.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/src/streaming/CMakeLists.txt  
main.cpp  
samplesConversion.cpp  
samplesConversionPerfTest.vcxproj → C:\Users\ngriesert\source\LimeSuiteNG\build\src\streaming\Release\samplesConvers  
ionPerfTest.exe  
Building Custom Rule C:/Users/ngriesert/source/LimeSuiteNG/CMakeLists.txt  
1\>  
– Install configuration: “Release”  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/embedded  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/embedded/lms7002m  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/embedded/lms7002m/lms7002m.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/embedded/loglevel.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/embedded/result.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/embedded/types.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/LMS7002M\_parameters.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/LimeSuite.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/CSRegister.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/DeviceHandle.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/DeviceRegistry.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/LMS7002M.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/LMS7002MCSR.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/LimePlugin.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/Logger.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/OpStatus.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/RFSOCDescriptor.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/Register.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/SDRConfig.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/SDRDescriptor.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/SDRDevice.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/StreamComposite.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/StreamConfig.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/VersionInfo.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/complex.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/config.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/limesuiteng.hpp  
– Installing: C:/Program Files (x86)/LimeSuiteNG/include/limesuiteng/types.h  
– Installing: C:/Program Files (x86)/LimeSuiteNG/lib/limesuiteng.lib  
– Installing: C:/Program Files (x86)/LimeSuiteNG/bin/limesuiteng.dll  
– Installing: C:/Program Files (x86)/LimeSuiteNG/lib/pkgconfig/limesuiteng.pc  
– Installing: C:/Program Files (x86)/LimeSuiteNG/bin/limeDevice.exe  
– Installing: C:/Program Files (x86)/LimeSuiteNG/bin/limeSPI.exe  
– Installing: C:/Program Files (x86)/LimeSuiteNG/bin/limeFLASH.exe  
– Installing: C:/Program Files (x86)/LimeSuiteNG/bin/limeTRX.exe  
– Installing: C:/Program Files (x86)/LimeSuiteNG/bin/limeConfig.exe  
– Installing: C:/Program Files (x86)/LimeSuiteNG/bin/limeOEM.exe  
– Installing: C:/Program Files (x86)/LimeSuiteNG/bin/limeGUI.exe  
– Installing: C:/Program Files (x86)/LimeSuiteNG/lib/cmake/LimeSuiteNG/limesuitengConfigVersion.cmake  
– Installing: C:/Program Files (x86)/LimeSuiteNG/lib/cmake/LimeSuiteNG/limesuitengConfig.cmake  
– Installing: C:/Program Files (x86)/LimeSuiteNG/lib/cmake/LimeSuiteNG/limesuitengConfig-release.cmake  
PS C:\Users\ngriesert\source\LimeSuiteNG\>

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I tried running LimeGUI and got the same missing dll error as before.

 ![image](https://canada1.discourse-cdn.com/flex034/uploads/myriadrf/original/2X/3/35a5b4c66c6347ed547700180b1069b30c03f1b2.png)

I think its time to look for a linux box… 🙂

---

<div class="post-metadata">

**Author:** ![RightHalfPlane](https://avatars.discourse-cdn.com/v4/letter/r/46a35a/32.png) [@RightHalfPlane](https://discourse.myriadrf.org/u/RightHalfPlane)\
**Post date:** [20 November 2024 02:46 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/16 "2024-11-20T02:46:22Z")

</div>

It is complaining that you do not have the 64 bit version of wxWidgets installed.

You also can run ubuntu on windows under WSL. Most of the information of how to do it is in -

Using the ANTSDR E200 on Windows with WSL Ubuntu 24.04

[![](https://img.youtube.com/vi/rckekxm25bg/maxresdefault.jpg "Using the ANTSDR E200 on Windows with WSL Ubuntu 24.04") ](https://www.youtube.com/watch?v=rckekxm25bg)

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [20 November 2024 12:10 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/17 "2024-11-20T12:10:16Z")

</div>

I’ve fixed the Windows DLLs placement, you can git pull latest changes and build.

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [20 November 2024 15:30 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/18 "2024-11-20T15:30:14Z")

</div>

Excellent! Thank you. That worked.

 ![image](https://canada1.discourse-cdn.com/flex034/uploads/myriadrf/original/2X/9/9f702c2e61f1821a62340d24b577d649add78cc8.png)

I am using radioconda with GRC 3.10.10.0.  
Fortunately, I have access to the Soapy LimeSDR Source/Sink, and I know that the Source is working at this point. From your previous feedback I understand that it isn’t feasible right now to have a more configurable block integrated in for Lime mini2.0 in window environment.

You did mention the possibility of saving a .ini file from the LimeGUI and using that somehow. I don’t see the option in the new LimeGui to save the ini file, and I don’t see the facility for calling it from GRC. I do see a “Device Arguments” field in the Soapy Source properties box. Is there any possibility of me being able to pass configuration data to the LIMESDRmini2 through here?

 ![image](https://canada1.discourse-cdn.com/flex034/uploads/myriadrf/original/2X/1/1a1b67c33fe4f7e3b70d05fd01c8ad01e9b575da.png)

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [20 November 2024 16:44 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/19 "2024-11-20T16:44:14Z")

</div>

Great, you got the LimeSuiteNG core working. Be aware that the Soapy LimeSDR Source/Sink that you’re using are still the ones that came with readioconda, they would still use legacy LimeSuite (v20.10.0-PothosSDR-2021.07.25-vc16-x64) which does not have LimeSDR Mini v2 support.

> [@ngriesert](#):
>
> From your previous feedback I understand that it isn’t feasible right now to have a more configurable block

What kind of parameters are you expecting?

> [@ngriesert](#):
>
> You did mention the possibility of saving a .ini file from the LimeGUI and using that somehow. I don’t see the option in the new LimeGui to save the ini file

Select the “LMS7002” node in the device tree on the left side of GUI, it will show you all controls.

> [@ngriesert](#):
>
> I do see a “Device Arguments” field in the Soapy Source properties box. Is there any possibility of me being able to pass configuration data to the LIMESDRmini2 through here?

Yes, Soapy block should accept argument “LOAD\_CONFIG=pathToIniFile”  
If Sink and Source blocks are using the same device, only one block needs the argument, otherwise config will be loaded twice.

---

<div class="post-metadata">

**Author:** ![ngriesert](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@ngriesert](https://discourse.myriadrf.org/u/ngriesert)\
**Post date:** [21 November 2024 04:10 UTC](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566/20 "2024-11-21T04:10:59Z")

</div>

I understand that the LimeSDR Source/Sink are not up to date. As I mentioned, the source is working for a simple FM receiver flow graph. I haven’t tried TX yet. It sounded like from your previous comments that the legacy LimeSuite might be ok for a lot of uses in GRC.

As far as parameters I’d like to be able to modify from the Source/Sink block, the first that comes to mind is the antenna setting i.e. LNAH vs LNAW. I see those selections are clearly and correctly documented for the mini2 in the LimeSuiteNG GUI. As I have looked at the various tuning parameters available in the LimeGUI (I honestly need to study them more), I am thinking that there are settings I may want to modify when operating the LimeSDR in a flowgraph. I know that with other receivers I have been able to configure test modes for direct sampling to pick up lower frequency signals and I suspect there are some test modes, or configuration bits that can be used to modify the range of receivable frequencies. I guess none of that really matters if I can just write a .ini file and load it up. I need to try that, and if that works I’m assuming I will have all of the configurability control that could be wanted…

I really appreciate all of the feedback and help! Thank you.

[Next page](https://discourse.myriadrf.org/t/limesuite-ng-installation-instructions-for-windows-11-limesdr-mini-2-0/8566.md?page=2)