[SVN Info] Doom Builder 2, GZDoom Builder, Builder64

Post a reply


This question is a means of preventing automated form submissions by spambots.
Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen: :angel: :angry: :beer: :bfg: :chaingun: :cheers: :blergh:
View more smilies

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

If you wish to attach one or more files enter the details below.

Expand view Topic review: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by NeoHippo » Fri Sep 12, 2014 22:59

Tiger wrote:... ask me for clarification when you need something further explained.
While everything else seems to fall into place quite nicely, there is one thing that still eludes me.
And that is, how is the chm file decompiled to html ? ADITI can find the HTML Workshop:

Image


At the moment, the help manual displays just question marks when accessed from within GZDB.

I could use an extermal CHMtoHTML converter, but that sort of defeats the purpose.

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by Blue Shadow » Fri Sep 12, 2014 18:36

Tiger wrote:Furthermore, if you would like to help out the DRDTeam by providing uploaded Developmental Builds of: GZDoom Builder, Doom Builder 2, and Doom Builder 64, please contact Eruanna or Enjay.
I was thinking of "applying" for this since I have a lot of free time on my hands, but I haven't got into the whole compiling source code for these editors, yet.

I'll probably give it a try soon.

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by Tiger » Fri Sep 12, 2014 17:44

Just FYI to all; I have officially stopped uploading developmental builds for: GZDoom Builder, Doom Builder 2, Doom Builder 64. For those that want to stay up to date and continue using the latest developmental builds:
  • For GZDoom Builder; follow-up on this thread
  • Be adventurous and compile it on your own using Bootless Star
Furthermore, if you would like to help out the DRDTeam by providing uploaded Developmental Builds of: GZDoom Builder, Doom Builder 2, and Doom Builder 64, please contact Eruanna or Enjay.

Regards,

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by Tiger » Tue Sep 09, 2014 14:28

Congrats! \o/

I am sure if the software wasn't CUI oriented, you would feel a bit more comfortable with it -- The CUI is a bit intimidating even with the most simple brain-dead applications. Feel free to explore around within the settings and - ask me for clarification when you need something further explained.

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by NeoHippo » Tue Sep 09, 2014 7:59

  • After a lot of typing, and trial and error processing, I believe that I finally got it to work.
Image
  • Thank you for your patience and for creating ADITI.

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by Tiger » Tue Sep 09, 2014 5:20

Here I have a bit of a problem:
If I follow your setup and type i and Enter, then two screens pop up,
this text screen
This behavior is expected. The program will open a new window on the desktop, - which from there the user can do a simple-drag-and-drop as explained in the instructions.
[johnCarmack]
The notice I find to be rather necessary as, believe it or not, Bootless Star's controlled environment is as safe as Windows 2.0 (stable than Windows 1 - excluding driver hell -, but still easy as hell to screw up as the environment is not 'knit-tight'), I don't think it is possible to make the environment any safer given the Batch shell environment. However, as long as the module is 'safe to use', then everything should be fine. And when worse comes to worse, (or those that are developing modules for this software) they can resort to using sub-processes which will avoid the Windows Batch Shell from killing itself from the most extreme complications.

Fun Fact: Did you know that it is possible that the Batch Shell can loose it's fork processes - including the root process, and that running this software in PowerShell can have intermittent and unexplained issues? Fun!
[/johnCarmack]

And now I am stuck. GZDoom Builder Dir - Not Found!.
Whatever I do, I can't get rid of that message.

The best answer I can give:
Configuring GZDoom Builder - Directory Setup
Keeping this short to only important topics, but do look around the settings and explorer what is available.
There is features that allows the Doombuilder Local Working Copy to be automatically updated before it is compiled and more, feel free to explore.
  • From the Main Menu in GZDoom Builder's module, go to Settings (Type: s key)
  • Go to Directory Setup (type: 5 key)
  • Go to 'Locate GZDoom Builder Directory' (type: 1 key)
  • Enter the path that contains GZDoom Builder's solution file within the Doom Builder project local working copy.
    • Within the working copy we just checked out from the step above, we need to tell this program where to find it.
    • As of today, you can find the solution file in: doombuilder\branches\GZDoomBuilder
      • [spoiler]Image[/spoiler]
What directory did you checkout the Doombuilder project onto your system?

Another problem I have is in trying to determine what directories and folders
are being or should be created during the setup procedure.
Can you elaborate a bit on this, I don't fully understand?
Do you mean when installing Bootless Star? If true, essentially, just extract the contents to any place you wish, but you can NOT put the software in the system directories (Windows directories, Program Files directories, and never in the Doombuilder SVN local working copy). The software will take care of itself and its environment, same as the modules (provided they follow the module and local directory rules). Though, I don't ever recall the user having to manually create directories or manipulate the program directly, other than Beta 1 through Beta 3....

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by NeoHippo » Tue Sep 09, 2014 2:07

Okay, I couldn't find where to enable the SVN command line tools, so I updated
TortoiseSVN to version 1.8.8 and made sure that those tools were enabled.

Then I gave it another try to install ADITI and got stuck again[/url].

I feel that I am getting closer, though. :)

[edit]
removed link

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by Tiger » Mon Sep 08, 2014 13:59

Great, you were able to compile the project just fine, baby steps :D
NeoHippo wrote:However, when running the generated build, I do not get the correct version number.
This is because you told the program to not fetch the latest revision ID. To change this setting, within the GZDoom Builder (.bat file) settings - go to 'SVN Settings' and then enable the 'SVN Master Control'. Enabling this (the rest can be false if you wish) alone allows the program to use the 'svnversion' command, which fetches the latest svn version from the project's repo. But, again, make sure that the TortoiseSVN Commandline tools are also installed (they are not by default); the program couldn't detect the SVN Commandline tools as that warning is telling me.

Image
NeoHippo wrote:I had saved the settings as wm.bat but the coreDefault.bat comes up every time.
Good, so you created a preset file. To load this preset file:
  • (From BootlessStar.bat only!)
  • From the Main Menu, go to User Configuration -- same place where you created the configuration file
  • Tell the program that you want to -load- a configuration file (typing 1 into the program)
  • And then type the preset filename; for example, wm
Every time you startup the program, you must go through this process of loading your configuration file. Once your configuration file is loaded, be sure that within the GZDoom Builder module, you also 'update' the preset to include the desired settings you want to save within the module.

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by NeoHippo » Mon Sep 08, 2014 7:24

After a lot of head scratching, I believe that I finally achieved the correct setup.
Although I am still not comfortable with it.
Spoiler:
However, when running the generated build, I do not get the correct version number.
The working directory says version 2020
Spoiler:
but the program says r1885
Spoiler:
How could I correct that ?

Also, about the preset.
I had saved the settings as wm.bat but the coreDefault.bat comes up every time.


[edit]
oh, great, now it cannot find the files anymore and I have to start over
Spoiler:
At least it worked once.
There is hope.

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by Tiger » Sat Sep 06, 2014 18:31

Any luck so far? If you still need help, we can try to meet on IRC, - probably meet up in #ZDoom (irc.esper.net).

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by Tiger » Thu Sep 04, 2014 12:45

Tiger wrote:Execute the GZDoomBuilder.bat moduleIn Bootless Star's Main Menu, go to: 'Run Project Modules' (type: 1 key)From the 'Run Project Module' screen, type GZDoomBuilderIf the module is not visible on the list, it must be first installed. Refer to Bootless Star 'Installing Modules', a few sections above from here.
Just enter the filename in the 'Run Project Module', this really just 'calls' the module you just put in that directory.
Image

NeoHippo wrote:After checking out the GZDoom Builder project from the SVN Database,
Image

If you already checked out the project (with the same folder name), you merely only updated your Local Working Copy -- everything is up to date and ready for use.

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by NeoHippo » Thu Sep 04, 2014 7:40

Tiger wrote: Working Copy Target - Critical Step

Configuring GZDoom Builder - Directory Setup
After checking out the GZDoom Builder project from the SVN Database,

Image

how do I get into the GZDoom Builder project Main Menu ?

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by Tiger » Thu Sep 04, 2014 2:18

I think the provided documentation maybe a bit - - - too verbose and not fully simplified. Some of the provided documentation is for those that want to create modules for Bootless Star or to modify the core, so not all of the documentation is created for general use in mind. What I am going to do is provide the steps in order to install and setup the program and the GZDoom Builder module (as it is actively developed at the time of this post). Whatever you learned from the overly complexed documentation that contains foreign jipperish, forget it about it for now.

To be sure there is NO confusion, I am going to start from the very beginning and work up -- and I'll try to keep it at a simplified language
<Note: I am going to start looking for video tutorial programs; walls of texts are no fun!>

Bootless Star
  • Installation
    • Download the latest version of Bootless Star (core)
      • CAUTION: The legacy is only available for those that need it specifically as the foundation and support with Ruby is completely different as opposed to the early beta builds. With that said, the Legacy version is outdated - unsupported and shouldn't be used for generalized use.
    • Create a new folder anywhere you wish; this folder will later contain the Bootless Star program (in the next step)
      • Do NOT create a folder in the Program Files or Program Files (x86)! Bootless Star is NOT designed to work in that environment!
        As of Windows Vista, programs can NOT write or control within that environment without needing Administrative permissions.
    • RECOMMENDED: Use 7Zip to extract the Bootless Star zip file to the newly created folder that was just created (the step above).
      • Required Step for Windows 8 and later with Windows ZIP (via Windows Explorer Shell): After extracting the contents from the .zip file, you _MUST_ unblock the 'BootlessStar.bat' file. Doing this, Windows will allow the program to execute and run normally, failure to do this step - Windows will NOT allow the program to execute at all.
    • Execute the BootlessStar.bat program and make sure it goes to the 'Main Menu' screen.
      • Possible failures:
        • Working Directory and Program Directory mismatch (or Hooking failure); when this error comes up, the program can not update the user's WD to match with the program's active directory. Please submit reports when this happens.
        • Operating System Compatibility issue; the program detected that the host system is not using Windows 2000 or later (NOTE: Windows XP is the minimum requirement; running the program under Windows 2000 is not possible and will crash prematurely). This program is not compatible nor supported with WINE for those under Linux flavor.


    Configuration - Directory Setup
    Keeping this short; most of the settings can be ignored unless the user wishes to be adventurous or power user.
    • Go to the Settings (type: s key) menu from the Main Menu.
    • Go to the Directory Setup option (type: 2 key)
      [spoiler]Image[/spoiler]
    • Look over what programs have not been detected by Bootless Star automatically.
      • Bootless Star will state what was detected and what was not detected. For example: "Detected: [ False ]"
      • True, Bootless Star was able to find this program or directory.
      • False, Bootless Star was not able to find this program or directory.
    • Select what was not detected and input the new desired location
      The in the next few sections will provide what GZDoom Builder (Doom Builder 2) requires
      • When entering a new location path, use _exact_locations_ (or Absolute Paths). Meaning, do NOT use: ".\MyLocation\someProgram.exe", instead use: "C:\Some\Path\Here\MyLocation\someProgram.exe".
        In addition, do _NOT_ in any circumstance use quotes. Bootless Star uses quotes in a entirely different purpose, when quotes are entered by the user the program will crash. If the path contains spaces and fancy characters, the program will automatically deal with those scenarios.
        [spoiler]Image[/spoiler]
    • Most projects will require Microsoft Visual Studio; from the Directory Setup Menu, go to "[1] Microsoft Visual Studio Category"
      [spoiler]Image[/spoiler]
      This will display what was detected and what was not detected. You shouldn't need to program this unless the user manually edited the system's global variable environment.
      If incase you need to edit these, please pay close attention to the instructions as the locations are bit different.


    Saving Configurations - Presets
    • From the main menu, go to: 'User Configuration' (type: 3 key)
      [spoiler]Image[/spoiler]
    • Save a new preset configuration file, by using 'Save Settings' (type: 2 key) and enter a new filename that you wish to use.
      • It is nearly essentially to create a new a configuration file as modules will not allow the user to save their configurations without having one already from the Bootless Star program.


    Installing Modules
    • From the Main Menu, go to 'Run Project Modules'
    • To install a new module, type: i.
      • A new window will appear on the desktop and Bootless Star will provide onscreen instructions.
        To install a module, simply put the '.bat' file of the module (for example: GZDoomBuilder.bat) in this window.
        [spoiler]Image[/spoiler]
    • Close the window that should now contain the .bat you dropped into the folder.
    • Press any key on the Bootless Star program to return to the Module screen.
    • Make sure that the module you have just installed is visible on the list of available modules.


------------------------------------
====================================
------------------------------------



GZDoom Builder (Project Module or Module)
  • Requirements

    Execute the GZDoomBuilder.bat module
    • In Bootless Star's Main Menu, go to: 'Run Project Modules' (type: 1 key)
    • From the 'Run Project Module' screen, type GZDoomBuilder
      • If the module is not visible on the list, it must be first installed. Refer to Bootless Star 'Installing Modules', a few sections above from here.


    Working Copy Target - Critical Step
    Checking out the Doom Builder project directly from the SVN Database Repo
    • Go to any folder you wish to put the 'Doom Builder' local working copy. This can be on your desktop, your home folder, wherever you wish.
      • NOTE: This is NOT the actual compiled program, but instead this contains the source code that makes this software possible to work.
    • Checkout the Doombuilder project
      • Using this address:

        Code: Select all

        https://svn.code.sf.net/p/doombuilder/code


    Configuring GZDoom Builder - Directory Setup
    Keeping this short to only important topics, but do look around the settings and explorer what is available.
    There is features that allows the Doombuilder Local Working Copy to be automatically updated before it is compiled and more, feel free to explore.
    • From the Main Menu in GZDoom Builder's module, go to Settings (Type: s key)
    • Go to Directory Setup (type: 5 key)
    • Go to 'Locate GZDoom Builder Directory' (type: 1 key)
    • Enter the path that contains GZDoom Builder's solution file within the Doom Builder project local working copy.
      • Within the working copy we just checked out from the step above, we need to tell this program where to find it.
      • As of today, you can find the solution file in: doombuilder\branches\GZDoomBuilder
        • [spoiler]Image[/spoiler]


    Update your preset
    • From the main menu, go to: 'Settings'
    • Select ' Update Saved Profile', (type: u key)
      • This will update your configuration with the latest changes. When this module is restarted, the configuration is automatically loaded during startup.


    Compile! - FINALLY!!!
    • From the main menu, select the following:
      • 1) Compile Core only
        • Generates the GZDoom Builder core program, help documentation only. Plugins are excluded
        2) Compile Core and Default Plugins
        • Generates the GZDoom Builder core program, help documentation, and default plugins.
        3) Compile Core and All Plugins
        • Generates the GZDoom Builder core program, help documentation, and all plugins (even unsupported ones).
      When failures occur, read the messages on the screen and investigate the issue. If compile errors occur, enable logging from the Bootless Star core (within the settings) and recompile the project while logging. The output messages could be useful for the developers for pin-pointing where the error occurred.

I hope these instructions helped, I have to stop now - I am about to sleep while I am keyboarding....

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by NeoHippo » Thu Sep 04, 2014 0:03

Thanks for all that information. Unfortunately it is way over my head.

Let me point you to what I have done so far.

[edit]
removed link

Re: [SVN Info] Doom Builder 2, GZDoom Builder, Builder64

by Tiger » Tue Sep 02, 2014 21:03

Wow version 1.1 :shock:
I can see why you have problems; please upgrade to Bootless Star 1.5.2 since the foundation has been re-wrote and is - generally much more improved. Your life will be much easier :D
In addition, be sure to fetch the latest versions of the modules aswell.

NOTE: You can not use your preset from version 1.1 with 1.5.2 due to identifier changes and the use of 'key chain' model.
Version 1.2 [revision 549]
==========================
--------------------------
19 Feb. 2014
----

[...]
* During the initialization period, the core will attempt to find the host system's .NET foundations.
* During the initialization period, the core will try to find Visual Studio, HTML Workshop, Inno setup, 7Zip, and SVN commandline tools.
[...]

Furthermore, when you run the Directory Setup setting (regardless of what program\module), just have the program point to the normal install directory path. For example, if you have 7zip installed on: C:\Program Files\7Zip\7za.exe, then tell the Bootless Star program to use that location. Hopefully you shouldn't need to go through these setups once you upgrade to v. 1.5.2. You will, however have to use the setup directory for the DB2\DB64\GZDB modules. To do this, just point the main project's solution root. Might be confusing for what I just said, but as of today, here's the links to use:
  • Doom Builder 2:
    • <pathToProjectsSVNLocalDirectory>\Doombuilder\trunk\
    Doom Builder 64:
    • <pathToProjectsSVNLocalDirectory>\Doombuilder\branches\Builder64\
    GZDoom Builder:
    • <pathToProjectsSVNLocalDirectory>\Doombuilder\branches\GZDoomBuilder\
    Examples:
    • C:\Users\Administrator\Doombuilder\branches\Builder64
      C:\Users\Guest\Doombuilder\trunk
      E:\Projects\Subversion\Doombuilder\branches\Builder64
      F:\Doombuilder\trunk
Once you have successfully setup the configurations for the module(s), just update your preset in the modules setting menu. Though, do be-sure you have first created a new preset file from 'Bootless Star' first, before saving from a module.

Moreover, besure that you have the Doombuilder local working copy on your host system. Bootless Star can not remotely fetch the contents from a server database, it will only use the local working copy that is provided by the user and system. Using PowerShell, you can use the SVN CUI toolset to do the following:

Code: Select all

cd ~;    # go-to your home directory -- this is really %UserProfile% identifier used in the system and the Batch shell.
mkdir ".\SVN Projects";     # make a new directory in your home, this will soon contain the Doombuilder contents
cd ".\SVN Projects";     # go-to our newly created directory

svn checkout https://svn.code.sf.net/p/doombuilder/code .\Doombuilder\;    # Here, we are pulling entire Doombuilder source into the specified path.  We will need this for Bootless Star.
PS_SVNCheckoutExample.png
If you receive an error when using the 'svn' command, besure that you have TortoiseSVN Commandline tools installed.

Top