Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[scamtank]

You're looking at the wrong branch - "master" is only for the last official release (which was quite a while ago), while "develop" has up-to-date stuff for 0.43.05.

No, I'm deffo pulling the development branch, the one with the x64-specific stuff. Running the generate-* batch files complains about not being able to find a CMakeLists.txt in the next folder up, like the old arrangement was. If I kick the .bat pile back to the \build folder like they used to be, it cannot find C/CXX compilers (line 22).

The whole process hasn't changed drastically from version 0.42 days, has it? With my level of skill, I'm reading compile.rst more like a spellbook than a manfile.

[lethosor]

Running the generate-* batch files complains about not being able to find a CMakeLists.txt in the next folder up, like the old arrangement was.

You must not be on the latest commit of the develop branch. Have you tried pulling again? What remote URL are you using? All of the .bat files should contain "cmake ..\..", i.e. two folders up. Check the file you're using to make sure that's the case.

[Rose]

No, he's right, the bat files were moved one folder down, but not modified to reflect the change. I'll upload a fixed version. +

I checked again, they're fine.

They were not. I have fixed them, they should be fine now.

I'm using develop branch and having issues building for x64.

I did:

Code: [Select]

.\build\win64generate-MSVC-gui.bat
Configure->Use default native compilers
Open dfhack.sln in VS2015
Build->Configuration manager
New x64 from win32 settings
Switch to Release configuration
Right-click INSTALL -> Build
I get a bunch of:

Code: [Select]

fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86'
Edit: Using Windows 7 64-bit. I might be way behind on Windows Updates since I reformatted the machine. Going to try updating.

There is no "win64generate-MSVC-gui.bat" in the build folder. If you have that, then you have the wrong branch of DFHack.

[lethosor]

Oh, I missed that they create a separate folder. I assumed it was "cmake .." before, like the others, but apparently not.

Anyway, here's an alpha release. It's not as stable as usual, and Ruby and Stonesense are missing (in at least some builds), but enough of it works that it's not entirely unusable.

If you're expecting DFHack to be stable for everyday use and don't want to (or know how to) provide helpful-enough feedback to fix issues, I wouldn't recommend using this build. I also don't recommend encouraging everyone else to use it, including it in packs, etc.. I know I say something like this with a lot of alpha builds, but I have less confidence with this one. Maybe it'll turn out to be somewhat stable, but there are many more opportunities for crashes that we haven't found yet, so don't count on it.

Also, back up your saves if you care about them! DFHack probably won't corrupt them even if it crashes, but don't count on it. (If you stick to exiting without saving with "die", though, it should be fine. Probably.)

[Bumber]

You did something wrong, then - there should only be an "x64" build configuration. Perhaps your version of CMake is out of date? I've got 3.6.1 and it works fine.

It's 3.6.1. Edit: Issue was out-of-date Windows.

There is no "win64generate-MSVC-gui.bat" in the build folder. If you have that, then you have the wrong branch of DFHack.

Just a typo. Should be "win64\generate-MSVC-gui.bat".

No, I'm deffo pulling the development branch, the one with the x64-specific stuff. Running the generate-* batch files complains about not being able to find a CMakeLists.txt in the next folder up, like the old arrangement was. If I kick the .bat pile back to the \build folder like they used to be, it cannot find C/CXX compilers (line 22).

I got that to work by running it from a cmd prompt sitting in the \dfhack directory. E.g., "C:\dfhack>.\build\win64\generate-MSVC-gui.bat". Then you can just select "\dfhack" as the source code directory (CMakeLists.txt is located here) from the GUI.

[Bumber]

After catching up on several Windows Updates, I now have a bunch of options for CMake configuration (including "Visual Studio 14 2015 Win64",) which weren't there before. This looks promising.

Edit: Seems to be working.

[Grax]

So now we have working DFHack for x64 and DT for x32 ;-)

I hope 43.05 x64 and x32 saves are 100% compatible.

[jecowa]

They should be compatible. No one has reported any problems so far. If the saves from the 32- and 64-bit versions ever become incompatible with each other, it would probably be because of a weird bug or something.

[Dirst]

They should be compatible. No one has reported any problems so far. If the saves from the 32- and 64-bit versions ever become incompatible with each other, it would probably be because of a weird bug or something.

...and then weaponized.

[lethosor]

So now we have working DFHack for x64 and DT for x32 ;-)

And 32-bit DFHack...

[Grax]

So now we have working DFHack for x64 and DT for x32 ;-)

And 32-bit DFHack...

32x dfhack?! Who does have it? I see here only 64x.

[lethosor]

https://github.com/dfhack/dfhack/releases

[Rose]

Is there a simple way to cancel jobs from within dfhack?

I'm working on editing dig designations from within Armok Vision, but I need to be able to cancel ones that have already been converted into jobs.

[Quietust]

Depending on the type of job, it might be possible to set the "item_lost" flag, which would cause it to cancel with "Job item lost or destroyed" - that's how the game handles (f)orbidding job items.

[Rose]

It's a digging job, so there's no item.

Could I set the job type to nothing?