Linux Steam- Creating new project doesn't create "UltraEngine.h"?

decay · October 21, 2021

It seems like it's a required file, but because this file doesn't exist, I can't really progress in using Ultra App Kit.

Josh · October 21, 2021

UltraEngne.h is part of the program files. The Linux project will load this header from the header search paths.

decay · October 21, 2021

7 hours ago, Josh said:

UltraEngne.h is part of the program files. The Linux project will load this header from the header search paths.

The issue is its not loading it. The project says it cant. I feel like some dependency isnt installed but Im not sure which one is needed.(I did install the ones listed in the tutorial)

Josh · October 21, 2021

Are you using Visual Studio Code?

decay · October 22, 2021

Yeah. I followed the instructions from the site as close as I could.

Josh · October 22, 2021

Maybe the path where Ultra App Kit is installed has a space in it? I thought it would work with spaces, but maybe GCC can't handle this?

Josh · October 22, 2021

Can you paste the contents of the file ".vscode/settings.json" from your project?

decay · October 22, 2021

{
    "makefile.extensionOutputFolder": "./.vscode",
    "makefile.alwaysPreConfigure": false,
    "makefile.launchConfigurations": [
        {
            "cwd": "/home/josh/Documents/Ultra Engine",
            "binaryPath": "/home/josh/Documents/Ultra Engine/AppKit",
            "binaryArgs": []
        },
        {
            "cwd": "/home/josh/Desktop/beta",
            "binaryPath": "/home/josh/Desktop/beta/AppKit",
            "binaryArgs": []
        },
        {
            "cwd": "/home/james/Documents/Ultra Engine/Projects/GUI Application",
            "binaryPath": "/home/james/Documents/Ultra Engine/Projects/GUI Application/GUI Application_d",
            "binaryArgs": []
        },
        {
            "cwd": "/home/james/Documents/Ultra Engine/Projects/GUI Application",
            "binaryPath": "/home/james/Documents/Ultra Engine/Projects/GUI Application/GUI Application",
            "binaryArgs": []
        }
    ],
    "makefile.configurations": [
        {
            "name": "Debug",
            "makeArgs": ["CONFIGNAME=Debug","PRODUCT_SUFFIX=_d","CONFIGFLAGS=\"-g -D_DEBUG\""]
        },
        {
            "name": "Release",
            "makeArgs": ["CONFIGNAME=Release","CONFIGFLAGS=-O2"]
        }
    ],
    "C_Cpp.default.configurationProvider": "ms-vscode.makefile-tools",
    "files.associations": {
        "array": "cpp",
        "atomic": "cpp",
        "bit": "cpp",
        "*.tcc": "cpp",
        "bitset": "cpp",
        "cctype": "cpp",
        "chrono": "cpp",
        "cinttypes": "cpp",
        "clocale": "cpp",
        "cmath": "cpp",
        "codecvt": "cpp",
        "complex": "cpp",
        "condition_variable": "cpp",
        "csignal": "cpp",
        "cstdarg": "cpp",
        "cstddef": "cpp",
        "cstdint": "cpp",
        "cstdio": "cpp",
        "cstdlib": "cpp",
        "cstring": "cpp",
        "ctime": "cpp",
        "cwchar": "cpp",
        "cwctype": "cpp",
        "deque": "cpp",
        "forward_list": "cpp",
        "list": "cpp",
        "map": "cpp",
        "set": "cpp",
        "unordered_map": "cpp",
        "unordered_set": "cpp",
        "vector": "cpp",
        "exception": "cpp",
        "algorithm": "cpp",
        "functional": "cpp",
        "iterator": "cpp",
        "memory": "cpp",
        "memory_resource": "cpp",
        "numeric": "cpp",
        "optional": "cpp",
        "random": "cpp",
        "ratio": "cpp",
        "string": "cpp",
        "string_view": "cpp",
        "system_error": "cpp",
        "tuple": "cpp",
        "type_traits": "cpp",
        "utility": "cpp",
        "fstream": "cpp",
        "future": "cpp",
        "initializer_list": "cpp",
        "iomanip": "cpp",
        "iosfwd": "cpp",
        "iostream": "cpp",
        "istream": "cpp",
        "limits": "cpp",
        "mutex": "cpp",
        "new": "cpp",
        "ostream": "cpp",
        "shared_mutex": "cpp",
        "sstream": "cpp",
        "stdexcept": "cpp",
        "streambuf": "cpp",
        "thread": "cpp",
        "cfenv": "cpp",
        "typeinfo": "cpp",
        "valarray": "cpp",
        "variant": "cpp"
    },
    "C_Cpp.errorSquiggles": "Enabled"
}

Josh · October 22, 2021

Thank you. Can you post the contents of the makefile in your project folder?

decay · October 22, 2021

ULTRAENGINEPATH = /home/james/.local/share/Steam/steamapps/common/Ultra App Kit
SRC = Source/*.cpp
FLAGS = -I/usr/include/freetype2 -I/usr/include/fontconfig -D_ULTRA_APPKIT "-I$(ULTRAENGINEPATH)/Include"
LFLAGS = -no-pie -lX11 -lpthread -lXft -lXext -lXrender -lXcursor -ldl
OUT = GUI Application$(PRODUCT_SUFFIX)

x64: $(SRC)
	g++ $(SRC) "$(ULTRAENGINEPATH)/Library/Linux/x64/$(CONFIGNAME)/AppKit.o" -o "$(OUT)" $(LFLAGS) $(FLAGS) $(CONFIGFLAGS)

clean:
	rm -f "$(OUT)"

Josh · October 22, 2021

According to this:

https://github.com/kriscross07/atom-gpp-compiler/issues/79

You might be able to make it work by inserting a forward slash before each space like so:

ULTRAENGINEPATH = /home/james/.local/share/Steam/steamapps/common/Ultra\ App\ Kit

decay · October 22, 2021

It still isn't working, unless I'm meant to clear the make cache or something afterwards. I restarted the project each time I changed the make file.

The exact error it gives btw is "cannot open source file "UltraEngine.h"". And I do see it in the program files like you mentioned, inside the include folder.

I feel like something here can easily be me not setting something up correctly, but I don't see any exact messages saying I need to install X thing, so im not quite sure what's happening.

decay · October 22, 2021

Something else is according to when you "build clean" it won't give an error but if you put the \ \ inside the make it ends up not being able to locate it, so I dont think it's having any issue getting to the folder

decay · October 22, 2021

It's actually building now, so the error seems to only be with the intellisense. I apologize for not noticing it's only an issue with the intellisense, although I dont know how I'll go about fixing that.

Josh · October 22, 2021

Oh yeah, there is a bit of a disconnect in vs code between the IDE and the compiler. I think there is a way to specify the header search path in one of the VSCode Jason files, just for intelligence.

Ma-Shell · October 23, 2021

I believe the one you need is the c_cpp_properties.json (https://code.visualstudio.com/docs/cpp/c-cpp-properties-schema-reference, https://code.visualstudio.com/docs/cpp/config-linux#_cc-configurations). There is an "includePath" setting there, which you will probably need to set correctly.

Josh · October 23, 2021

C++ support in VSCode is quite new. I think we can expect the situation to be constantly improving.

Azure_Zero · December 9, 2021

This may need to be included as a troubleshooting section of the reference page.

I also have the UltraEngine.h problem with VS code, Now I got further in getting a sample program to run with Code::Blocks IDE but hitting an issue with X11\X11Xmu\WinUtil.h

Flop · February 21, 2022

Hey everyone,

I just started installing the ultra app kit on my linux machine (manjaro) and had the same issue. Since it took me a while to piece everything together, I thought it might be a good idea to update this thread so future linux user might have it easier.

As the moment of this post the recommended c++ plugin for visual studio code is not available on the market place so you need to install it via .vsix file. The file can be downloaded on the official marketplace website under "Version History". After downloading and installing the plugin you can repeat the steps @Ma-Shell mentioned above and edit the c_cpp_properties, by directly accessing the json file and or using the corresponding interface.

There are three things we need to consider when editing the properties files:

1. Check the compilerPath variable. If you using the the x64 build target the compiler should be g++. (e.g. "usr/bin/g++").

2. Add the missing include path. Since the UltraEngine.h file is not located inside the workspace we have to add the path manually to the "includePath" variable. Simply copy and paste the value of the "ULTRAENGINEPATH" variable in the makefile and add it to the includePath array.

3. Check the provider variable. In my case the "configurationProvider" was set to the wrong provider, it should be "ms-vscode.cpptools". More infos about this here.

Hope this helps. GL coding.

One more note here. Depending on the operating system you are on, you might get a follow up error that the openal dependencies are not not found by the application. In this case check where the al.h file is located in your system. In my case it is located under /usr/include/AL and i had to adjust the file path in the framwork.h files of the ultraengine from "include openal/al.h to include AL/al.h" (line 129 - line 130) same goes for the alc header.

jmf · March 5, 2022

On 10/21/2021 at 1:21 AM, decay said:

It seems like it's a required file, but because this file doesn't exist, I can't really progress in using Ultra App Kit.

On 10/22/2021 at 10:38 AM, Josh said:

Oh yeah, there is a bit of a disconnect in vs code between the IDE and the compiler. I think there is a way to specify the header search path in one of the VSCode Jason files, just for intelligence.

I've found that opening up the file intellisense isn't detecting will usually solve the issue pretty quick as long as the IncludePath is set properly.

If you get an issue where the #include says one of it's includes can't be opened, ctrl + click into the #include to open it up, prioritizing intellisense's parsing of that specific file. If you make structural changes of nearly any size, it can confuse the heck out of intellisense and take forever to catch up with the changes, red squiggling everything. sometimes when this happens, I ctrl+shift+p start typing intellisense, and click "restart intellisense for active file", or if you made huge changes, "reset intellisense database". I absolutely hate the way vscode handles intellisense.

The important thing to note with vs code is that intellisense is not connected to the linker, unless you use cmake and select the option to configure intellisense with cmake.. So you can see red squiggles when intellisense can't find the file even though the makefile is configured properly. Using cmake doesn't solve the problem though, unfortunately. it's far superior to make for a few reason, but the relevant one is because if you have a designated "build" directory, you can just delete the build directory when intellisense loses it's mind, and save the CmakeLists file to auto generate the cmake files that intellisense uses when configured with cmake.

Hopefully that's clear and makes sense.

Sign In

Linux Steam- Creating new project doesn't create "UltraEngine.h"?

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation