Nay

No you don't, Leon. All that is required is TDB_full_434.05_2013_07_17.sql (available in the forums' download section) and all the SQLs from TrinityCore_4.3.4_DB_Alpha/tree/master/updates

Paste cmake and compile log

Can't confirm. What did you import to the DB before world_updates.sql?

I'll take the opportunity to re-use this topic to announce a new dev. Welcome to the jungle team!, Joschiwald (https://github.com/TrinityCore/TrinityCore/commits?author=joschiwald)

MrSmite: go troll somewhere else, PLEASE Depa Marco: we are aware of the db errors. If you wanna help fixing them, submit fixes to https://github.com/TrinityCore/TrinityCore_4.3.4_DB_Alpha/ (either PR or issue)

The guide works however you have to do git checkout 1b8d917ea9 in the core repo because that's the hash of the last database sync (https://github.com/TrinityCore/TrinityCore_4.3.4_DB_Alpha/commit/25736316c80c72fccc11943917a64f54274ed753) Anyway, I'll release TDB 4.3.4_5 and TDB 3.3.5_52 today or tomorrow.

+maestro: Well, no problem, it's fixed now. That specific compiler error was not triggered on our buildbot, that is known to be "very bitchty" regarding builds, but our other bot, Aokromes, quickly spotted this topic and forwarded it to me. It seems that this error was changed on GCC 4.5 (hopefully), before that it's a simple warning "warning: cannot pass objects of non-POD type ‘struct std::string’ through ‘...’; call will abort at runtime".

Fixed on efdbc68caea5dbe5f9dcdc8, update. This kind of issues should be posted on the issue tracker.

Nowhere, Ricky. What compiler are you using?

Ar you using attachments or going with "Image" button that shows a window named "Image Properties" with a field for URL?

This has nothing to do with Git. What compiler are you using? MSVC is the only compiled supported on Windows.

1366x768 here, no issues

Exactly but, yet again, no one to do it.

Razor needs to stop whatever he is doing. http://collab.kpsn.org/display/tc/FactionTemplate this page is fine Edit: old page deleted and moved to FactionTemplate.dbc P.S I don't have time to fix everything. When you see something wrong click Edit page, it's easy.

Not a browser issue, just a bad conversion from old wiki. If you find an issue you can comment on the page with the problems or, even better, edit the page directly. Anyway, Scripts tc2 page fixed. (Image embedding works fine if you get a *direct* link to the image. http://imageshack.us/f/811/tcwiki.jpg/ is not a direct link http://img811.imageshack.us/img811/1615/tcwiki.jpg is a direct link)

test test

Github issue, related to the error at https://github.com/TrinityCore/TrinityCore/commits/master

Should be fine now. And please stop reporting errors about 4.3.4 branch, it's not meant to be used. --- Canned message start --- It appears the issue in the original post was solved, so this thread shall be closed. Should you encounter any other difficulties, please open a new thread. --- Canned message end ---

I invoke the power of google to present you this: http://stackoverflow.com/questions/10888391/link-fatal-error-lnk1123-failure-during-conversion-to-coff-file-invalid-or-c

> Git was NOT FOUND on your system - did you forget to install a recent version, or setting the path to it? So... install Git and update your PATH environment variable (google it up if you don't know how to do it)

Read http://collab.kpsn.org/display/tc/Installing+TDB+4.3.4 carefully.

> Updated the core and recompiled... I got the extractors this time around.. but they don't work with the 64 bit windows.. so cannot extract.. lol.. wtf.. Please define "don't work" (what's wrong?), because tools for Windows in 64 bits is definitely working here.

You should not mix 4.3.4 TC with 3.3.5 TC, the instructions to install are different for both. Follow http://collab.kpsn.org/display/tc/How-to_Win (for 3.3.5) carefully and you will succeed.

You got me lost...

For fresh source, assuming you got TDB 50, all of the .sqls in sqlupdatesworld Characters and auth updates are not required for fresh compiles. Now, that said, next time you *update*, you will need to import all the *new* .sqls that are in world, characters, and auth (take notes of the last sqls imported) (personally, I wipe and import the whole world db every update; I don't do that for characters nor auth but the number of .sqls for those two DBs is way less than world)