[support]

Hi,

Thanks for your feedback. We have extensively tested our IntelliSense engine with the auto variables, nested classes and template classes and could not reproduce the problems you are reporting. Furthermore, many of our users reported that they are successfully using the Clang IntelliSense engine with complex C++11 code. Hence it looks like the problem on your side is caused by some configuration issue (e.g. incompatible CFLAGS, missing include directory, or some very specific statement that breaks IntelliSense). We will be happy to help you solve it, but we would need more information on reproducing it.

Could you reproduce it on a stand-alone project and send it to us? If not, could you send us a screenshot of the problem along with the CFLAGS/CXXFLAGS from the project view in the Clang IntelliSense Diagnostics console?

[support]

Hi,

We have provided a solution in this post.

[support]

Hi,

It looks like the Espressif guys forgot to declare this function in their SDK. Please feel free to add the following declaration to espmissingincludes.h and include the file from your projects:

int os_printf_plus(const char *format, ...)  __attribute__ ((format (printf, 1, 2)));

[support]

Hi,

No problem. We have updated our Beaglebone tutorials to clearly state the Angstrom is deprecated and also published a new tutorial showing how to create an app for Beaglebone.

If you encounter further problems or find outdated information in our documentation, feel free to let us know so that we could update the documentation or provide fixes/workarounds.

[support]

Hi,

Please try version 3.0. It supports VirtualBox 5.0+.

[support]

Hi All,

Please try version 3.0. It supports Windows 10 with the normal vminstall tool.

[support]

Hi,

Perhaps some libraries are missing in the sysroot. Please try our latest Beaglebone toolchain. It also contains the pre-built Qt binaries, so you can simply deploy them to your Beaglebone and start using Qt.

We have also published the final version of the tutorial: http://visualgdb.com/tutorials/beaglebone/qt5/cross-compile/

You should be able to create an app for it by following the Raspberry tutorial without cross-compiling the entire Qt framework (note that Qmake in the toolchain has the c:\SysGCC\Beaglebone directory hardcoded; our next tutorial will show how to adjust it, but for now please place the Beaglebone toolchain to c:\SysGCC\Beaglebone).

[support]

Hi,

OK, we have retested the qt cross-compilation with Beaglebone. You need to edit the device configuration file to remove the -mfloat-abi argument and also change the QT_QPA_DEFAULT_PLATFORM.

Please have a look at this tutorial preview for more details. We will run a clean build to recheck everything and then publish the final tutorial. We will also release an updated toolchain with the pre-built Qt binaries, so you can simply wait for that if you don’t want to build it yourself.

[support]

Hi,

OK, regarding the registry traces, Windows keeps the track of all devices that it recognizes, including the WinCDEmu drives. Same would happen if you plug in USB stick. We could add some special cleanup mechanism to remove them, but why? Windows is designed that way and it does not really cause any trouble to users.

With cmd output, it happens because the WinCDEmu executable is a ‘GUI Mode’ executable and cmd.exe does not wait for it to terminate. You can work around it by creating a .bat file with the following contents:

%~dp0\PortableWinCDEmu %*

Then just run the .bat file instead of the .exe file and cmd will handle it correctly.

/CreateISO is just a convenient shortcut for running mkisofs.exe; if you want to use it from command-line, you can just download it here and you don’t need any extra tools for that.

We don’t need to compile the project in every language, but we need to customize the translation system to allow embedding the .lng files into the portable executable. Currently we don’t have the resources to do that, so we are waiting for someone from the community to contribute a pull request.

[support]

Hi,

Thanks a lot for the log. Looks like we have nailed it now: http://sysprogs.com/files/WinCDEmu/WinCDEmu-4.1.exe

Let us know if this resolves the problem.

[support]

Strange. Could you please share the log file from the new DLL? Is should help us locate the problem.

[support]

Hi,

We have found a bug in the code responsible for reading language files, but we have fixed it in the 4.1 build. Just to do a clean check, could you try to restore the langfiles, install 4.1 and replace the x64\WinCDEmuContextMenu.dll with this DLL, i.e.:

1. Rename the old WinCDEmuContextMenu.dll to WinCDEmuContextMenu.old
2. Copy the new DLL into the x64 folder
3. Restart (or kill all instances of explorer.exe via task manager and re-run it)
4. Delete the WinCDEmuContextMenu.old to ensure that it’s not loaded into Explorer
5. Check whether the bug still happens and see if the log file contains anything different.

Does the bug still happen (langfiles needs to be in place)?

 

[support]

Hi,

Looks like the problem might be caused by the translation engine. Can you try temporarily deleting the c:\Program Files (x86)\WinCDEmu\langfiles folder and restarting? Does this solve the problem?

[support]

Hi,

Thanks, this is strange. Please try uninstalling 4.1 and installing this build. It should create a log file and show what is going on.

[support]

Hi,

Have you tried uninstalling WinCDEmu 4.0, restarting and installing WinCDEmu 4.1? Perhaps the old plugin was still loaded.

If this does not help, could you try running the instrumented build here and sending us the %LOCALAPPDATA%\WinCDEmuLog.txt file? It should explain what causes the crash.

[Author]

Posts