|
|
|
So, I've uninstalled my python 3 and re-installed it as a 64-bit version (from ), redone all the pip stuff, copied libclang.dll from my QT installation, now I (still?) get:
[ 18%] Generating datacopy.cpp Traceback (most recent call last): File "C:\****\Python39\lib\site-packages\clang\cindex.py", line 4173, in get_cindex_library library = cdll.LoadLibrary(self.get_filename()) File "C:\****\Python39\lib\ctypes\__init__.py", line 452, in LoadLibrary return self._dlltype(name) File "C:\****\Python39\lib\ctypes\__init__.py", line 374, in __init__ self._handle = _dlopen(self._name, mode) OSError: [WinError 193] %1 is not a valid Win32 application Mike |
|
|
|
|
||
|
Quote:
Don’t it too seriously, it’s just a release Codename ;-) |
|
|
||
|
|
|
Mike B,
I do my builds on a windows machine in Docker under WSL2. That saves me from the headache of creating a build chain with the exact right version of everything installed. https://docs.microsoft.com/en-us/win...wsl-containers I use this Docker image: https://github.com/EdgeTX/build-edge...sts/Dockerfile Jesper |
|
||
|
Quote:
The Wiki Win10 instructions are tested multiple times on a Win 10 PC that is installed fresh with all the updates. It might be that you have some older files or settings in the way that are interfering. What I can guarantee with confidence is that when you run the steps listed in EdgeTX Wiki on a freshly installed Win 10, then they end up in success. This might not be the ideal answer, as you likely are not eager to setup your PC new, but you could, just to see that it works, setup a VM with Win10, let all MS Updates play and then run the steps from the Wiki build env guide and it will most likely work without hickups. But, as I already said previously - if you find a way how to make building more streamlined/simplified, I am all for it. Everybody wins. But would need input how to achieve this, as what I wrote in Wiki is the shortest I was able to come up with that produced radio firmwares that run on radio the same, as when built under Ubuntu (the EdgeTX default build env in GH Docker). |
|
|
Last edited by Risto; Jun 22, 2021 at 07:35 AM.
|
|
|
|
|
It looks like python won't load the libclang.dll. This is the script segment causing the error:
def get_cindex_library(self): try: library = cdll.LoadLibrary(self.get_filename()) except OSError as e: msg = str(e) + ". To provide a path to libclang use " \ "Config.set_library_path() or " \ "Config.set_library_file()." raise LibclangError(msg) return library I've checked the file name (self.get_filename()) and it is "libclang.dll", and I've also forced it to be "C:\windows\system32\libclang.dll", where I have put the dll, and I still get the error. My current guess is the libclang.dll I have is a 32-bit dll and python is looking for a 64-bit one. The one I have is dated 04/12/2017. I copied it from my QT installation (which is version 5.9). QT looks like it is reporting it is a 32-bit version, from the "about" menu. I'm now trying to locate a 64-bit version of the dll. Mike Edit: Found one, I extracted it from a LLVM installation, so now the build gets a bit further. The data copy is reporting an error: thirdparty/STM32F4xx_DSP_StdPeriph_Lib_V1.8.0/Libraries/CMSIS/Include\core_cm4.h:1515:1: error: unknown type name '__STATIC_INLINE' |
|
Last edited by Mike Blandford; Jun 22, 2021 at 09:10 AM.
|
|
|
|
At this point I'm using 7.2.1, as that is the one I have installed and I am using to build erskyTx. I don't really want to change it and then have problems with my erskyTx builds.
It handles core_cm4.h when compiling erskyTx. I can try installing the one shown in the instructions, while keeping the one I'm using available. I appreciate what you say about a clean build, but I'm really looking to add being able to build directly. I also will want to be able to do incremental builds, change one file, compile it and link, not build everthing again. Personally, I fail to see why the source files need to be copied anywhere. Surely they should be able to be compiled from where they are. My opinion is if the only way this compile will work is if you have to create a dedicated (virtual?) machine with a very specific set of tools, then the compile method needs to be simplified. Mike |
|
|
|
|
|
Hi Mike,
you can easily install GNU Arm Toolchain v10 2020-q4, that we use in EdgeTX, in parallel to other version GNU Arm toolchain (I also even have 4.7 2013 q3 installed to still be able to compile OTX 2.3...). None of the GNU Arm Toolchains need to be in system PATH for the build to succeed. |
|
|
|
||
|
Quote:
|
|
|
||
|
|
|
I did a post earlier that seems to have vanished!
I've installed the recommended toolchain, now I get more errors. I have set the cmake parameter to use this toolchain, and its include directories. I also changed to 1 processor so the output is more readable. This is the start of the errors: Code:
[ 30%] Generating datacopy.cpp C:\******\arm-none-eabi\include\sys/syslimits.h:40:9: warning: 'ARG_MAX' macro redefined [-Wmacro-redefined] datastructs.h:26:10: note: in file included from datastructs.h:26: C:\******\arm-none-eabi\include\inttypes.h:18:10: note: in file included from C:\******\arm-none-eabi\include\inttypes.h:18: C:\******\arm-none-eabi\include\sys/_intsup.h:19:10: note: in file included from C:\******\arm-none-eabi\include\sys/_intsup.h:19: C:\******\arm-none-eabi\include\limits.h:6:10: note: in file included from C:\******\arm-none-eabi\include\limits.h:6: C:\******\arm-none-eabi\include\limits.h:142:9: note: previous definition is here C:\******\arm-none-eabi\include\sys/syslimits.h:52:9: warning: 'PATH_MAX' macro redefined [-Wmacro-redefined] datastructs.h:26:10: note: in file included from datastructs.h:26: C:\******\arm-none-eabi\include\inttypes.h:18:10: note: in file included from C:\******\arm-none-eabi\include\inttypes.h:18: C:\******\arm-none-eabi\include\sys/_intsup.h:19:10: note: in file included from C:\******\arm-none-eabi\include\sys/_intsup.h:19: C:\******\arm-none-eabi\include\limits.h:6:10: note: in file included from C:\******\arm-none-eabi\include\limits.h:6: C:\******\arm-none-eabi\include\limits.h:146:9: note: previous definition is here A bit later in the errors there is a reference to errors in .h files that are in "C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0", so what is looking in there I don't know (yet). I've got a few more things to try, I'm checking all paths to include files etc. Mike Edit: Tried a few changes, the above type of error is still there, this is the sort of error I also see: Code:
C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um\winnt.h:2482:15: error: '(anonymous struct at C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um\winnt.h:2482:15)' cannot be defined in a type specifier datastructs.h:27:10: note: in file included from datastructs.h:27: targets/horus\board.h:26:10: note: in file included from targets/horus\board.h:26: targets/common/arm/stm32\board_common.h:103:10: note: in file included from targets/common/arm/stm32\board_common.h:103: targets/horus\../simu/simpgmspace.h:25:10: note: in file included from targets/horus\../simu/simpgmspace.h:25: C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um/windows.h:171:10: note: in file included from C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um/windows.h:171: C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\windef.h:24:10: note: in file included from C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\windef.h:24: C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\minwindef.h:182:10: note: in file included from C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\minwindef.h:182: C:\******\arm-none-eabi\include\sys/cdefs.h:265:33: note: expanded from macro '__alignof' C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um\winnt.h:17420:7: error: expected ')' datastructs.h:27:10: note: in file included from datastructs.h:27: targets/horus\board.h:26:10: note: in file included from targets/horus\board.h:26: targets/common/arm/stm32\board_common.h:103:10: note: in file included from targets/common/arm/stm32\board_common.h:103: targets/horus\../simu/simpgmspace.h:25:10: note: in file included from targets/horus\../simu/simpgmspace.h:25: C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um/windows.h:171:10: note: in file included from C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um/windows.h:171: C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\windef.h:24:10: note: in file included from C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\windef.h:24: C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\minwindef.h:182:10: note: in file included from C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared\minwindef.h:182: thirdparty/STM32F4xx_DSP_StdPeriph_Lib_V1.8.0/Libraries/CMSIS/Device/ST/STM32F4xx/Include\stm32f4xx.h:2398:43: note: expanded from macro 'CRC' C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um\winnt.h:17420:7: note: to match this '(' thirdparty/STM32F4xx_DSP_StdPeriph_Lib_V1.8.0/Libraries/CMSIS/Device/ST/STM32F4xx/Include\stm32f4xx.h:2398:30: note: expanded from macro 'CRC' #ifndef __GNUC__ #include <windows.h> So this looks like __GNUC__ is not defined when doing the datacopy. |
|
Last edited by Mike Blandford; Jun 22, 2021 at 05:06 PM.
|
|
||
|
It's the name of a ship... sheesh!Quote:
The goal has been clearly outlined... it has been to get development of features moving again, as more than 1.5+ years for something as 'basic' as touchscreen support is just ludicrous. If you don't want it fine, but it still hasn't happened in OTX. Will 2.4.0 be a polished release? No, there will be some rough edges. Will there be bugs - some, but mostly in the form of some features missing, and hence disabled, or the odd 'cosmetic' glitch. There should be nothing that will effect the control of your model. Will it replace OTX? Not yet, but who knows what the future will bring. This is the first release for the project, give the project time to develop a community, for the core team to form a plan on it's future, have more people testing and contributing, and then see what happens. |
|
|
||
|
|
|
Do you mean why can't you change it. For this first release, the theme (including splash screen) has been embedded into the firmware, so that it is possible to start with a blank SD card without loosing any of the graphics (such as splash screen, menu icons, default theme, etc). A future release (presumably the next) will re-enable being able to load theme from the SD card, as well as choosing custom splash screen, etc.
Edit: And I'll remove foot from mouth, next post explains where you can put the custom splash image. I was thinking of the B&W radios, completely forgetting the color lcds are different. |
|
Last edited by pfeerick; Jun 24, 2021 at 04:20 AM.
|
|
||
|
Quote:
|
|
|
||
|
||
|
Quote:
|
|
|
||
Thread Tools | |
Similar Threads | |||||
Category | Thread | Thread Starter | Forum | Replies | Last Post |
Discussion | Official OpenTX version 2.3 Discussion Thread | pafleraf | Radios | 10531 | Apr 14, 2024 03:01 AM |
Discussion | Pixhawk 2 (un)official discussion thread | Rusty105 | Multirotor Drone Electronics | 212 | Aug 15, 2023 09:26 PM |
New Product | Official - DJI Mini 2 - ***Owners Thread*** 4K OcuSync 2.0 | Justapoke | Multirotor Drone Talk | 103 | Dec 10, 2022 11:21 AM |
Discussion | Official OpenTX version 2.2.3 Discussion Thread | RC Grouper | Radios | 32 | Jun 11, 2019 08:59 AM |
Discussion | Official Drone Registration Discussion Thread **Discussion Here** | bansheerider | Model Aircraft & Drone Advocacy | 4320 | Dec 07, 2017 01:53 AM |