Posts by dawlane

    If you don't already know by now. A backdoor was introduced into one of the main upstream repositories that every x86_64 Linux distribution relies on. It was only discovered by chance by some one working for Microsoft that noticed ssh logins were taking longer by a few milliseconds. They traced it down to the xz compression tool where the malicious code was very cleverly hidden in a test binary.

    What is more surprising is how this backdoor got into the repository. It looks like author of this code actually managed to take over the upstream xz repository by social engineering, possibly by themselves or in collusion with others to get the original maintainer to give them access to do their own commits.

    External Content
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    2. Did also try this from v2022-03-26 but got this (slightly more useful) error message and gave up immediately [IMG alt="1710135788670.png"]…88670-png.1627/[/IMG]

    That indicates that it failed to load a plugin found in the platforms folder.
    set QT_DEBUG_PLUGINS=1 should show output to the command line terminal when Ted is ran from it.

    The Qt folders are:

    The shared libraries and binaries are:

    There maybe a qt.conf file that sets the paths for Qt related stuf.

    I don't have much to go on here :)

    The event viewer should give a more detailed reason why an application failed to start.

    Try installing Microsoft C++ 2015-2022 runtime. Ted should have been built against Visual Studio 2019.
    Check that the Qt plugins are loading by opening a command prompt and type:

    If that fails, then your only options are:

    1. To try to build Ted against an older version of Visual Studio; requires a Visual Studio Dev Essentials account. And an older version of the Qt SDK. Use QtCreator directly to open C:\cerberus\src\ted\, set the build to release and build.
    2. Download an older version of Ceberus, delete all Qt runtime files for and Ted out of C:\cerberus\bin\ and copy over the Qt runtimes and Ted from the older version.
    3. Rebuild the whole of Cerberus. See C:\cerberus\src\docs\BUILDING_WINNT.txt. NOTE: If I remember, requires the minimum Powershell 5. See here.
    4. Update you system to Windows 10.

    As Windows 7 is no longer supported, you are pretty much on your own.

    My ball is in learning the Odin language at the moment

    May have to check that out. Been toying around with Haxe and OCaml.

    Had a look at Lazarus IDE 3.0. It still sucks, and I don't think they will ever get it to work constantly across each platform.
    Their moto of "Write Once.... Compile Everywhere" kind of makes them a bit of a laughing stock with old package that don't work still in the distribution and application crashing at random. And an application you are trying to debug, shouldn't crash the IDE.

    If he makes a 3D library, I'll certainly take a look.

    I remember everyone being promised a 3D library for BlitzMax. That if I recall didn't end well.

    You won't see java if it's installed with Android Studio. The JDK that comes with it, is only for that version.
    You will only see it system wide if the environment paths are set to the installation of the one in Android Studio.
    The process is some thing like this:
    From the task bar search, type environment: environment and select the Edit the system environment variables button.
    In the System Properties dialogue box, under the Advanced tab click the Environment Variables button.
    In the User variables for .... click New
    Enter in the Variable name: JAVA_HOME
    Enter in the Variable value: C:\Program Files\Android\Android Studio\jbr

    In the User variables for .... Select the item called Path and click the Edit button.
    Select the Variable value edit box and add %JAVA_HOME%\bin; to the beginning of the line.
    Tip: Hit the Home key on the keyboard to go to the front of the line after selecting the edit box.

    Click the OK button and open up a terminal and test out if the path works.

    What is the difference between the two ways of specifying the -version parameter?

    Passing the show setting properties will show everything on that java installation.

    I also saw that you can do javac -version, does that work as well? How is JDK and Java different?

    The difference is that Java is solely a runtime, where as the other is the Java Development Kit, which not only contains the compiler and development files, but also contains a runtime.

    I also saw that you can do javac -version, does that work as well?

    Not normally with it being the java compiler, e.i. compiles java sources into byte code (aka p-code) and will only show the java version number.

    The author of these modules need to be contacted to see if they are willing to release the sources to github and change any licence to something that's more friendly to commercial enterprises.

    All that would be needed then is JSON file containing the modules, download URLs and licence information that transcc can read to pull in the modules.

    The transcc command line: transcc_{HOST} -modget={module_name|All} -modlic={ALL|zlib|mit|gpl}.

    Transcc downloads JSON from CX repo and check if it's newer, else uses local if unavailable.

    The current documentation for desktop targets on MS Windows states the requirements be either MinGW, or MS Visual Studio should be installed.

    The first thing to note is that Cerberus X will work with Visual Studio 2022, providing that the MSVC v142 - VS 2019 C++ x64/x86 build tools to be installed with whatever is the latest WindowsSDK 10/11. If you wish to use any older versions of Visual Studio or any old versions of Build Tools for Visual Studio, then you will need to have a Microsoft account with the Visual Studio Dev Essentials subscription; this should be a free.

    The general installation process, that is providing that you have the necessary hard drive space, is to run the Visual Studio Installer. And when it presents you with the components to install, you select the Desktop development with C++ workload along with the aforementioned MSVC v142 - VS 2019 C++ x64/x86 build tools optional component. The optional component isn't required if using the Visual Studio Installer for Visual Studio 2019.

    Installing the Visual Studio IDE tool suite gives you the ability to load the Cerberus project into Visual Studio, where you can profile and debug the actual C++ code.

    But if hard drive space is limited, then you can just download the Build Tools for Visual Studio.
    NOTE: Using the normal Visual Studio installer will not work correctly to just install the build tools with the following below.

    If using the Build Tools for Visual Studio 2022, then download aforementioned Build Tools for Visual Studio 2022. Make sure that the Windows File Explorer is set to show file extensions and create a new text file called msvc2022CXLoadout.vsconfig, and copy, paste and save the code below.

    You then need to open a terminal and change directory to where the Build Tools for Visual Installer was downloaded to and type:

    vs_BuildTools.exe --config "FULL_PATH_TO_/msvc2022CXLoadout.vsconfig"

    The Visual Studio Installer should show something like:

    The Windows SDK can be changed to suit. The default is to use Windows 10, which should be good for a long while yet.
    Leave the installation locations as they are, unless you know what you are doing.

    The last thing that needs to be modified is the MSBUILD_PATH config variable to where MSBuild is located. You will find this in the config.winnt.txt file located in the Cerberus bin directory. Change it to:

    MSBUILD_PATH="${PROGRAMFILES(x86)}\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin\MSBuild.exe"

    If someone has the Build Tools for Visual Studio 2019, then follow the same process as for the Build Tools for Visual Studio 2022, but save the code below int a file called msvc2022CXLoadout.vsconfig.

    The MSBUILD_PATH should then be modified to:

    MSBUILD_PATH="${PROGRAMFILES(x86)}\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\MSBuild.exe"

    You can then use either #CC_USE_MINGW=False or #GLFW_USE_MINGW=False in a source file depending on the desktop target.