Announcement

Collapse
No announcement yet.

[TOOL] Create your own binary build for your team

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

  • started a topic [TOOL] Create your own binary build for your team

    [TOOL] Create your own binary build for your team

    I just made a small app that can help you build binary version of UE4 from source build.



    Download (with source): http://wp.me/p2fInN-rW
    Last edited by ryanjon2040; 03-29-2017, 02:17 AM. Reason: Updated to 1.2

  • replied
    Has there been any news in that discord channel about any possible ways to fix the PDBCopy pathway issue? Everytime I click that link it just takes me to the add friends page of discord for some reason.

    Leave a comment:


  • replied
    I managed to change that line and it looked like it worked basically once i rebuilt that specific thing. And then it got past the stripping part where the previous error was. For some reason visual studio seems to have a pretty different file pathway than what that line believed it to be, but that's not the end of my problems unfortunately. I got a whole slew of new errors that I have absolutely no idea what the heck mean. There's quite a bit of error messages that popped up. This is the first line it says, but then goes into a lot of line numbers in different files.

    Program.Main: ERROR: AutomationTool terminated with exception: AutomationTool.AutomationException: BUILD FAILED: failed, retries not enabled:
    AutomationToolProcess exited with code 1


    Just out of curiosity though, how long does it generally take to make an installed build? Cause it seemed to be pushing about 50 minutes before it stopped with errors relating to whatever else it has some problem with.

    I'm going to attempt tomorrow to build a different engine version release as a test with the file modification to test to see if it will give me the same errors. I did find it odd that when I was watching it, I saw it try to parallel execute a certain file about 50 times. I was a little confused. PCLaunch.rc is what I think it might've been called.



    Also I can't see the discord channel. It just sends me to the add friend page for some reason instead of the channel. Maybe it's private? I would love to check in on a discord channel that might help.

    Edit: Tried anther different release build. Same thing. It's probably because of that one line change I did so ill just keep looking for a way around the PDBCopy thing without changing that pathway it has in there. Hopefully someone in the discord channel has had some kind of thing with this happen and knows what to do.
    Last edited by dragon3582; 08-19-2017, 01:58 PM.

    Leave a comment:


  • replied
    Originally posted by dragon3582 View Post
    Yea I looked through that post already. It didn't really help me much. I did however find out exactly where the path is being set in the source code. The thing I'm wondering now is, can i change it to be the pathway I need it too without messing much stuff up?

    It's in the WinPlatform.Automation.cs script on line 370. I can change that line specifically to be the pathway it should try to look for, but it does contain spaces in the folder names. I'm not sure if putting "Microsoft Visual Studio" and other folder with spaces like that into the file pathway name if it might cause it to throw me an error. I also don't know if i can just change this line, save, and then retry the binary tool and hope for the best. Would you happen to know these couple things?
    You can try changing that one line and see if it helps. I haven't faced an issue like this before so not sure what's wrong. I have linked your post on discord so you can check there if someone got an idea on how to fix this issue. https://discordapp.com/channels/1872...99439008923648 (Discord does not feature direct link to message so open that link and search for PDBCopy.exe)

    Leave a comment:


  • replied
    Yea I looked through that post already. It didn't really help me much. I did however find out exactly where the path is being set in the source code. The thing I'm wondering now is, can i change it to be the pathway I need it too without messing much stuff up?

    It's in the WinPlatform.Automation.cs script on line 370. I can change that line specifically to be the pathway it should try to look for, but it does contain spaces in the folder names. I'm not sure if putting "Microsoft Visual Studio" and other folder with spaces like that into the file pathway name if it might cause it to throw me an error. I also don't know if i can just change this line, save, and then retry the binary tool and hope for the best. Would you happen to know these couple things?
    Last edited by dragon3582; 08-18-2017, 01:51 AM.

    Leave a comment:


  • replied
    [MENTION=304993]dragon3582[/MENTION] This thread might help https://forums.unrealengine.com/show...un-pdbcopy-exe

    Leave a comment:


  • replied
    Alright it finally rebuilt itself and stopped at the end.

    ERROR: Failed to start local process for action ("The system cannot find the file specified"): C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\PDBCopy.exe "D:\UE4_Custom\Engine\Binaries\Win64\Android\UE4Editor-Android_ASTCTargetPlatform.pdb" "D:\UE4_Custom\Saved\Engine\Binaries\Win64\Android\UE4Editor-Android_ASTCTargetPlatform.pdb" -p
    Program.Main: AutomationTool exiting with ExitCode=1 (Error_Unknown)

    I'm guessing it's a problem with visual studio here as I installed it on my D drive. My directory has the PDBcopy, but it's in the v15.0 folder instead of the v12.0 because there is no v12.0 folder.

    Edit: I reinstalled Visual Studio in the C drive in hopes it would generate the files in the specified location, but it seems that it's still in a way different directory than what the compiler thinks it's supposed to be at. If I could change where it thinks the PDBCopy file is, that would solve my issue. But I have no idea where to start looking for where it tries to get that directory from.
    Last edited by dragon3582; 08-17-2017, 08:32 PM.

    Leave a comment:


  • replied
    Originally posted by dragon3582 View Post
    Ah i see. Do you still want me to try the batch file or will this version of the binary builder pause at the end to show me the error?
    Try the new binary builder. That will work .

    Leave a comment:


  • replied
    Ah i see. Do you still want me to try the batch file or will this version of the binary builder pause at the end to show me the error?

    Leave a comment:


  • replied
    Originally posted by dragon3582 View Post
    Yea I did run the automation tool from the binary builder. It just closed and opened the command prompt. I'll save that as a batch file and try to run it tomorrow. It takes around 40 minutes to get through everything before failing for some reason. I'll see if this script can help me shed some light on this build fail and ill get back to you on what it did.
    I just checked the download link and I think you are using the old version. i just updated the download link so please download the app from this link and you should now see the log window like in the first post. http://bit.ly/UE4_BinaryMaker

    I only updated the git source and forgot to update the actual download to the new one. Sorry for the confusion.

    Follow the same steps as mentioned above and you should now see the error that's causing the build to fail.

    Leave a comment:


  • replied
    Yea I did run the automation tool from the binary builder. It just closed and opened the command prompt. I'll save that as a batch file and try to run it tomorrow. It takes around 40 minutes to get through everything before failing for some reason. I'll see if this script can help me shed some light on this build fail and ill get back to you on what it did.

    Leave a comment:


  • replied
    Originally posted by dragon3582 View Post
    1. When the binary builder runs, it doesn't frame the command prompt window inside of the binary builder like the picture at the top. It just closes it and the command prompt comes up and begins running through it.
    Did you run AutomationTool from inside Binary Builder? You have to select the AutomationTool.exe inside the Binary Builder application and after selecting you have to click the Build button. This program will then run AutomationTool.exe with given parameters and displays the output inside the log window to the right.

    Originally posted by dragon3582 View Post
    2. At the end the command prompt closed suddenly, but i managed to make out it saying warning with some red text by it.
    To overcome this issue what I used to do before creating this app was I created a bat file that executed AutomationTool.exe manually and then put a pause command at the end. This prevented the CMD window from closing automatically.

    For example, here is an example content. You save the below stuff as a bat file and then run this:
    Code:
    "\Engine\Binaries\DotNET\AutomationTool.exe" BuildGraph -target="Make Installed Build Win64" -script=Engine/Build/InstalledEngineBuild.xml -set:WithDDC=false -set:HostPlatformOnly=true -set:SignExecutables=false -NoSign
    pause
    Originally posted by dragon3582 View Post
    3. Still no LocalBuilds folder.
    Because your build is failing for some reason.
    Last edited by ryanjon2040; 08-17-2017, 01:30 AM.

    Leave a comment:


  • replied
    Hm. Alright, after a couple days I came back to this to try it again following those steps and I did exactly the steps you described. But three things happened that I'm sure are not right.

    1. When the binary builder runs, it doesn't frame the command prompt window inside of the binary builder like the picture at the top. It just closes it and the command prompt comes up and begins running through it.
    2. At the end the command prompt closed suddenly, but i managed to make out it saying warning with some red text by it.
    3. Still no LocalBuilds folder.

    At this point I'm assuming it's the engine version I downloaded. There was a customized version that I wanted to use that has some cool toon shading options in the material editor. Not sure why it doesn't want to compile this, and I can't even see what happened at the end of the automation tool command prompt to see what failed if anything. There was a size bump somewhere as it went down 11gb. Which seems about right for an engine build. But it's not in the engine folder of localbuilds like its supposed to be.

    Edit: I just downloaded the normal 4.16.3 release code and tried to do the steps. Still no Local builds folder and the above steps happened again, although I can't confirm the warning this time because it disappeared too fast. I really don't know what I might be doing wrong here. Can you point me in the right direction here [MENTION=904]ryanjon2040[/MENTION] ?
    Last edited by dragon3582; 08-15-2017, 10:32 PM.

    Leave a comment:


  • replied
    @dragon3582,

    I just checked the InstalledEngineBuild.xml in promoted branch and the Local Installed Directory is still in your root directory like this:

    Code:
    <Property Name="LocalInstalledDir" Value="$(RootDir)/LocalBuilds/Engine/Windows"/>
    The actual process of using this tool is like this:

    1: Download Unreal Source.
    2: Run Setup.bat.
    3: Get a coffee and wait till setup.bat finishes.
    4: Run GenerateProjectFiles.bat.
    5: Open UE4.sln
    6: In Solution Explorer under Programs, right click on AutomationTool and select build. This will build and create the AutomationTool.exe.

    Once all the steps above are done, you can start this app and select the AutomationTool exe file, check the options and Build. The log at the right side gives you the output of AutomationTool so you can see if the build failed or no.

    Hope this helps.

    Leave a comment:


  • replied
    I came across this while trying to create a binary build, but as I started looking for the Automation tool exe I realized I didn't have that exe anywhere. Is AutomationTool.exe supposed to be the right thing to find? I see UnrealBuildTool, but that's about it.

    Edit: I tried to run a batch file previously mentioned in another post. I went to the bathroom and came back to my computer restarted. Not exactly sure what happened, but after that there was the automation tool exe in the folder mentioned here. I tried using the build tool this time and it went through the entire process I'm assuming, but as what duke said, I didn't get a LocalBuilds folder. It doesn't seem to have made one anywhere that I can see. Does this tool still work with 4.16.3 builds [MENTION=904]ryanjon2040[/MENTION] ?
    Last edited by dragon3582; 08-11-2017, 05:48 PM.

    Leave a comment:

Working...
X