In order to avoid:
Command line warning D9025 : overriding '/EHc-' with '/EHc'
with DDK/WDK projects in the sources file specify
USE_NATIVE_EH=1
instead of
USER_C_FLAGS=$(USER_C_FLAGS) /EHsc
Monthly Archive for June, 2009
So Microsoft offers a downgrade to the Windows 7 pre-predecessor Windows XP for everyone buying a computer until end of April 2011. Nice.
Maybe the fellows at Redmond should take a minute or two and ask themselves why people are so reluctant to upgrade to Windows Vista and Windows 7. While Windows Vista was generally said to be slower and bulkier, the same holds for Windows 7 from my tests of the Beta and the RC. It’s also very nice to have an operating system and not require the amount of disk space a Vista or Windows 7 wants you to have. Apart from that older Windows versions did have a way to get rid of components you didn’t like. Nowadays it’s merely possible to deactivate such components, but it doesn’t seem to free any disk space whatsoever. Just like when buying Nero Burning ROM and expecting to get a CD/DVD-recording software and not a fancy-shmancy multimedia program suite, I expect my operating system to offer me the support to run the compatible programs. Sadly all this bulky and fancy-shmancy stuff comes already with the “lower” Windows editions, so no actual choice there either.
But the killer argument against Windows 7 for me is the lack of the classic start menu. As much as others may like the fancy new start menu, be it in XP, Vista or Windows 7 … I hate all of these. And up to and including Vista I could simply return to my classic start menu setting – which, by the way, is one of the first steps along with adjusting the Windows Explorer “Folder Settings” and autocompletion in console windows on any freshly installed Windows. I (and after a web search it seems I’m by far not alone) have yet to find a way to make this happen. Oh yeah, not to mention that the new start menu looks gross once you turn off the fancy styles/themes.
Too bad Microsoft decided to scrap it. However, the “customizable” new start menu is probably more of a PR gag than a brilliant example of usability. But well, Redmond does it and we follow, right? I guess no more.
// Oliver
Nun ist es passiert. Hier auf Island ist ein scheinbar braver Bürger in Álftanes mal ausgerastet. Das in 2003 erbaute Eigenheim legte er mit einem gemieteten Bagger in Schutt und Asche und begrub sein Auto gleich noch dazu im Vorgarten. Ursprünglich hatte er einen Kredit über 34 Millionen Isländische Kronen aufgenommen (in ausländischer Währung), hat durch diesen und die Kursschwankungen mittlerweile aber 76 Millionen Kronen zurückzuzahlen (trotz der bisherigen Zahlungen).
Die Aufräumarbeiten kann man hier bewundern.
Sein Kommentar war, dass sich die Banken wie Terroristen gerierten und er sich nur zur Wehr setze. Ob seine Frau, die im Ausland arbeitet, schon davon weiß, war nicht zu erfahren.
// Oliver
So far when using screen I was always using very simple steps and using the simplest features. But given that PuTTY doesn’t feature tabs, it’s pretty cool what you can do with screen. You can either start one or multiple screen sessions with one or multiple windows and then have them running even across your SSH sessions. Now most people probably know that. However, Ubuntu lately introduced a nice supplement called screen-profiles in the 9.04 release and to be renamed to byobu for the next one. It provides some really nice information within each screen session (and window) that can make the work with screen so much more useful. Have a look here.
Now I found this by chance because I was showing screen to Friðrik on his newly installed Ubuntu 9.04. Since I personally use the LTS version or Debian, I hadn’t seen it before.
// Oliver
… werden sich bei der sog. Europawahl wohl so einige gedacht haben, als sie begannen den Wahlzettel von oben her durchzulesen. Und das wird auch der Grund sein, warum soviele schon da hängen blieben.
Ich schlage vor die Aufstellung der Parteien auf dem Wahlzettel mal testweise komplett umzudrehen. Theoretisch sollte es ja keinen Unterschied machen … also gibt es sicher auch keine Einwände, oder etwa doch? 
// Oliver
The comments are enabled again for most posts. Sorry that it took longer than anticipated. But now I’m up-to-date with WordPress
Sometimes you want to build potential goals of nested make files, i.e. make files that reside in a different folder. The best method I’ve been able to come up with so far was this one:
# Declare some (immediate) constants (uppercase) and
# (deferred) local variables (lowercase)
NEED_GMAKE_VERSION := 3.80 3.81
MAKE_VERSION_MAJOR := $(word 1, $(subst ., ,$(MAKE_VERSION)))
MAKE_VERSION_MINOR := $(word 2, $(subst ., ,$(MAKE_VERSION)))
# Do not allow to run on versions of GMAKE whose
# capabilities we don't know
$(if $(filter $(MAKE_VERSION),$(NEED_GMAKE_VERSION)),,\
$(error This makefile requires one of the following GNU make \
versions: $(NEED_GMAKE_VERSION)))
# The goals
MAKE_DIRECTORIES = folder1 folder2
.PHONY: all
all: $(MAKE_DIRECTORIES)
.PHONY: $(MAKE_DIRECTORIES)
$(MAKE_DIRECTORIES):
@$(MAKE) --keep-going --directory=$@ $(MAKECMDGOALS)
# All goals "forward" the make into the individual directories
.PHONY: $(MAKECMDGOALS)
$(MAKECMDGOALS): $(MAKE_DIRECTORIES)
Even if you don’t know the available goals in nested make files, this top-level make file will go into folder1 and folder2 and do its job. No matter whether you told it to make clean, make all or simply make.
// Oliver
PS: Of course you need not hard code the folders … they could also be retrieved by a find call.