http://morison.biz/technotes/ Each article also has its own newsfeed. en 2006-2008, Rod Morison Software technotes@morison.biz Sat, 04 Jul 2009 04:35:19 GMT Yet Another Community System http://blogs.law.harvard.edu/tech/rss 70 http://morison.biz/technotes/comments/10 http://morison.biz/technotes/comments/10 I had to manually add a link "sudo ln -s /var/spool/postfix/var/run/mysqld /var/run/mysqld" to make web-cyradm run I had to manually add a link "sudo ln -s /var/spool/postfix/var/run/mysqld /var/run/mysqld" to make web-cyradm run Web-Cyradm Install Fri, 29 May 2009 02:42:02 GMT http://morison.biz/technotes/comments/9 http://morison.biz/technotes/comments/9 Very good! One of the very few howtos that actually work One minor addition: the login test didn't work, I had to manually modify access right (sudo chmod g+r /etc/ssl/private) to get rid of "unable to get private key from '/etc/ssl/private/ssl-cert-snakeoil.key'" Very good! One of the very few howtos that actually work One minor addition: the login test didn't work, I had to manually modify access right (sudo chmod g+r /etc/ssl/private) to get rid of "unable to get private key from '/etc/ssl/private/ssl-cert-snakeoil.key'" Postfix & Cyrus Install Fri, 29 May 2009 01:12:30 GMT http://morison.biz/technotes/comments/8 http://morison.biz/technotes/comments/8 hi there I have a ubuntu machine (Hardy Heron). It does not have smtptest and imaptest. Can't seem to use apt-get to install them. I have googled for info on how to install them but no luck. How do I install them? thanks hi there I have a ubuntu machine (Hardy Heron). It does not have smtptest and imaptest.

Can't seem to use apt-get to install them. I have googled for info on how to install them but no luck. How do I install them?

thanks Gordon Postfix & Cyrus Install Thu, 21 May 2009 13:58:48 GMT http://morison.biz/technotes/comments/7 http://morison.biz/technotes/comments/7 i do not find the mentioned winxp.vc9.manifest... there is only a winxp.manifest in the current distribution of sources of wxPython with this one, i get an error message, when trying to run mt.exe as mentioned in your article: mt.exe:general error c101008c:Failed to read the manifest from the resource of file "python.exe". Der angegebene Ressourcenname wurde nicht in der Image-Datei gefunden. last sentence is german and means "Given resource name was not found in image-file" thanks for any help Kuhlschrank i do not find the mentioned winxp.vc9.manifest...

there is only a winxp.manifest in the current distribution of sources of wxPython with this one, i get an error message, when trying to run mt.exe as mentioned in your article: mt.exe:general error c101008c:Failed to read the manifest from the resource of file "python.exe". Der angegebene Ressourcenname wurde nicht in der Image-Datei gefunden.

last sentence is german and means "Given resource name was not found in image-file"

thanks for any help

Kuhlschrank Kuhlschrank WxPython 2.8 Vista 64 bit crash - workaround found Fri, 16 Jan 2009 05:23:44 GMT http://morison.biz/technotes/comments/6 http://morison.biz/technotes/comments/6 I finally resolved the issues I had when trying to call runner.exe within the Visual Studio 2003 environment using a Post-Build Event. No output would show in the Build window (runner.exe was built using --runner=ParenPrinter). The problem arose because my runner.exe depends on some external DLLs. The WINDOWS DLL runtime search order is: the parent directory of the executable, some system directories, and then the directories listed in %PATH%. I did not realize that Visual Studio does NOT use environment variables, like %PATH%, added or modified after VS has been installed!!!! It should be noted however that when running your program in the Debugger from within the IDE, it DOES use updates to the environment in place when the IDE is started. Even if you start devenv.exe from a shell, as opposed to a shortcut, the Post-Build event has no knowledge of changes to your environment that were made after installation. Only the geniuses at Microsoft can explain this behavior. What this means is that external DLLs that are needed to run your test, and which you added to your PATH variable, are not available when the Post-Build event executes. There are 2 solutions. The better option is to add the necessary env vars and update the path in a batch file that calls runner.exe. For example, place the following in a postbuild.cmd file located with your source code and call it in the Post-Build event: set QTDIR=c:\someplace\qt\WINDOWS path = %PATH%;%QTDIR%\debug\lib runner.exe The other solution is to add an entry to the VS Tools->Options->Projects->C++ Directories dialog when the the "Show Directories for:" dialog says "Executable Files". To match the above batch script, the entry would be c:\someplace\qt\WINDOWS\debug\lib. I prefer the former since what is going on visible and explicit instead of being hidden in one of the dozens of dialogs in the IDE. I finally resolved the issues I had when trying to call runner.exe within the Visual Studio 2003 environment using a Post-Build Event. No output would show in the Build window (runner.exe was built using --runner=ParenPrinter).

The problem arose because my runner.exe depends on some external DLLs. The WINDOWS DLL runtime search order is: the parent directory of the executable, some system directories, and then the directories listed in %PATH%. I did not realize that Visual Studio does NOT use environment variables, like %PATH%, added or modified after VS has been installed!!!! It should be noted however that when running your program in the Debugger from within the IDE, it DOES use updates to the environment in place when the IDE is started. Even if you start devenv.exe from a shell, as opposed to a shortcut, the Post-Build event has no knowledge of changes to your environment that were made after installation. Only the geniuses at Microsoft can explain this behavior.

What this means is that external DLLs that are needed to run your test, and which you added to your PATH variable, are not available when the Post-Build event executes.

There are 2 solutions. The better option is to add the necessary env vars and update the path in a batch file that calls runner.exe. For example, place the following in a postbuild.cmd file located with your source code and call it in the Post-Build event:

set QTDIR=c:\someplace\qt\WINDOWS path = %PATH%;%QTDIR%\debug\lib runner.exe

The other solution is to add an entry to the VS Tools->Options->Projects->C++ Directories dialog when the the "Show Directories for:" dialog says "Executable Files". To match the above batch script, the entry would be c:\someplace\qt\WINDOWS\debug\lib.

I prefer the former since what is going on visible and explicit instead of being hidden in one of the dozens of dialogs in the IDE. Gail CxxTest setup for the Visual Studio IDE Sat, 20 Sep 2008 08:39:20 GMT http://morison.biz/technotes/comments/5 http://morison.biz/technotes/comments/5 On a related note, CxxTest has a new home: cxxtest.tigris.org Also, there is a Wiki for CxxTest at: cxxtest.com And here is a link to a slightly updated user's guide On a related note, CxxTest has a new home: cxxtest.tigris.org

Also, there is a Wiki for CxxTest at: cxxtest.com

And here is a link to a slightly updated user's guide kfitch CxxTest setup for the Visual Studio IDE Tue, 09 Sep 2008 09:54:23 GMT http://morison.biz/technotes/comments/4 http://morison.biz/technotes/comments/4 This article describes exactly what I am trying to do. The problem is that in the post-build step, the tests do not appear to run inside VS.NET 2003. Not only that, I cannot get any output from the tests to appear in the IDE output window whether or not the test fails. The pre-build works fine and it generates an executable that works properly when run in a cmd shell - that is the output from the cxxtest suite is shown properly. I wrote two simple tests one of which fails: TS_FAIL("ERROR"). The other always passes: TS_ASSERT(1 == 1); My pre-build command is: cxxtestgen.pl -o MyTest.cpp --runner=ParenPrinter MyTest.h My post-build command is 3 lines: echo "Run test" MyTest.exe echo "Test Completed" The echoes work fine. Thank you Microsoft If you have any ideas I would be grateful for the help! Thanks. This article describes exactly what I am trying to do. The problem is that in the post-build step, the tests do not appear to run inside VS.NET 2003. Not only that, I cannot get any output from the tests to appear in the IDE output window whether or not the test fails. The pre-build works fine and it generates an executable that works properly when run in a cmd shell - that is the output from the cxxtest suite is shown properly.

I wrote two simple tests one of which fails: TS_FAIL("ERROR"). The other always passes: TS_ASSERT(1 == 1);

My pre-build command is: cxxtestgen.pl -o MyTest.cpp --runner=ParenPrinter MyTest.h

My post-build command is 3 lines: echo "Run test"

MyTest.exe

echo "Test Completed"

The echoes work fine. Thank you Microsoft

If you have any ideas I would be grateful for the help! Thanks. Gail CxxTest setup for the Visual Studio IDE Fri, 05 Sep 2008 10:15:11 GMT http://morison.biz/technotes/comments/2 http://morison.biz/technotes/comments/2 Ok, goody Ok, goody testy Test B Mon, 03 Sep 2007 02:42:29 GMT http://morison.biz/technotes/comments/1 http://morison.biz/technotes/comments/1 Test B received Test B received rod Test B Mon, 03 Sep 2007 02:38:44 GMT