Announcement

Collapse
No announcement yet.

[TOOL] [Tut] [Win] Unreal Qt Creator Project Generator v0.3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • replied
    How can I add unreal source code to the project? UnrealEngine does it untomaticaly for VS. This is like almost the only thing that is missing to me.

    Edit 1:
    Also support for plugins would be great.
    Last edited by Krzysiek_TATE; 08-31-2017, 08:33 AM.

    Leave a comment:


  • replied
    Version 0.3 beta released

    So, I finally got some spare time to work on the tool and here it is:

    The beta of the highly improved version 0.3

    Highlights:
    • The generation process is now fully automated (configuration only during first run).
    • The tool should now also work for custom builds of UE4 (git version)
    • Fixed problems with perforce (thanks to Ypsylon)
    • Bug fixes
    • Executable renamed to uProGen.exe (easier to type in cmd)

    Note: For optimal usability I recommend adding this tool's folder to the PATH variable.
    You can then just execute uProGen from a CMD window inside your project folder and it will require no further input for the generation.
    (Of course you can still enter the project path manually when launching the tool from a non-project folder)

    Note: This will most likely be the last major version of the tool as I consider it more or less complete.

    Note: I have only tested this version on my computer. Bugs can be reported on GitHub. The source code of this version can be found in the testing branch of the repository.

    Leave a comment:


  • replied
    The epic could implement this tool in the unreal, qt creator is much better than Visual Studio for C ++

    Good hint about doxygen

    Thanks for sharing

    Leave a comment:


  • replied
    It would make much more sense to implement this kind of tool in python, as command-line script, instead of using C#.

    That would make it portable and it would probably take less time as well.

    Leave a comment:


  • replied
    I just submited pull request for qtBuildPreset.xml just little change but pretty important for perforce users :-)

    Btw for the next version I have planned to introduce a manual configuration file where the user can set engine path and the Qt environment hash. The project file could be detected from the working path of the tool -> Then you could just run the tool inside your project directory and it would do its magic without user interaction (if a valid configuration is detected, otherwise it would display the normal dialogues).
    Good news :-)

    Leave a comment:


  • replied
    Originally posted by Ypsylon View Post
    Thanks for this tool dude! It was realy lifesaver for me as i can finaly work in some realy IDE instead of VS :-)

    Thanks for source too, made some small changes (updated build and run configuration so projects can use ue4 perforce plugin), wanna change how it handles unreal engine paths so developers using custom engine build can use this great tool.

    Wanna ask how should i handle my commits, should i create new branch so u can review them and merge them later to new version?
    I'm a first time GitHub user so I'm no expert but yes (according to the docs) I think you should fork the repo, apply your changes (maybe in a new branch) and then submit back a pull request. Then I can pull your changes in if I agree with them (as soon as I've got some spare time, I'm a little busy at the moment). Just please make sure that you comment your changes and do some testing before submission.

    Thanks for your participation

    Btw for the next version I have planned to introduce a manual configuration file where the user can set engine path and the Qt environment hash. The project file could be detected from the working path of the tool -> Then you could just run the tool inside your project directory and it would do its magic without user interaction (if a valid configuration is detected, otherwise it would display the normal dialogues).
    Last edited by AlphaN; 10-20-2015, 12:34 AM.

    Leave a comment:


  • replied
    Thanks for this tool dude! It was realy lifesaver for me as i can finaly work in some realy IDE instead of VS :-)

    Thanks for source too, made some small changes (updated build and run configuration so projects can use ue4 perforce plugin), wanna change how it handles unreal engine paths so developers using custom engine build can use this great tool.

    Wanna ask how should i handle my commits, should i create new branch so u can review them and merge them later to new version?

    Leave a comment:


  • replied
    Thanks for this tool! It works except that the debugging is really slow (it takes a long time for Qt to update variable in the "Locals and Expressions" panel).

    I followed steps 4-5 and added the CDB symbol paths in "tools/options/Debugger" (and replaced YOUR USERNAME by my username of course):

    Code:
    symsrv*symsrv.dll*C:\Users\<YOUR USERNAME>\AppData\Local\Temp\symbolcache
    cache*cache*C:\Users\<YOUR USERNAME>\AppData\Local\Temp\symbolcache
    I use CDB from windows kit 8.1.

    Leave a comment:


  • replied
    Originally posted by SalahAdDin View Post
    Work this in linux?
    No this tool only supports Windows.
    But doesn't the Unreal Build Tool generate QtCreator projects (and projects for other IDE's) out of the box if you are on Linux?
    Last edited by AlphaN; 09-07-2015, 01:27 PM.

    Leave a comment:


  • replied
    Work this in linux?

    Leave a comment:


  • replied
    Really appreciate that you share you tool with us. Good Work!

    Leave a comment:


  • replied
    Originally posted by maikklein View Post
    I am on Windows 10 x64 and I removed the quotes manually. It seems to be stuck in a loop because it can't find the engine for some reason.
    I uploaded a new version, manual entry of Unreal Engine path should now work.

    Edit: Never mind

    Update: v0.2d2 now stores your manual engine path input in a file so you only have to enter the path once. Registry-based detection was removed because it wasn't compatible with newer versions of UE.
    Last edited by AlphaN; 09-01-2015, 03:43 PM.

    Leave a comment:


  • replied
    Originally posted by AlphaN View Post
    Does execution of the tool continue or does it abort with this message? If it does continue, then you can ignore the message (It seems to be a missing if statement and I'll fix it)
    Just a question, are you on 32-Bit Windows? Which Windows version? Because this might be a reason the registry read fails, otherwise you wouldn't have to enter the path manually.

    Edit: Sorry there is another bug, I didn't remove the quotation marks which are added automatically when you drag and drop a folder to the cmd window from the --> The directory is not found when I try to read it

    Thank you for your feedback
    I am on Windows 10 x64 and I removed the quotes manually. It seems to be stuck in a loop because it can't find the engine for some reason.

    Leave a comment:


  • replied
    Originally posted by maikklein View Post
    Any ideas?
    Does execution of the tool continue or does it abort with this message? If it does continue, then you can ignore the message (It seems to be a missing if statement and I'll fix it)
    Just a question, are you on 32-Bit Windows? Which Windows version? Because this might be a reason the registry read fails, otherwise you wouldn't have to enter the path manually.

    Edit: Sorry there is another bug, I didn't remove the quotation marks which are added automatically when you drag and drop a folder to the cmd window from the --> The directory is not found when I try to read it

    Thank you for your feedback
    Last edited by AlphaN; 09-01-2015, 01:55 PM.

    Leave a comment:


  • replied
    Unreal Engine 4 installation not found, please enter Unreal Engine 4 base directory (that one with the 4.x folders in it):
    D:\Epic Games
    Directory contains no Unreal Engine installations.
    Any ideas?

    Leave a comment:

Working...
X