![]() Add in C/C++|Additional Include Directories: "I:\Program Files (x86)\Microsoft DirectX SDK (November 2008)\include"ġ3. Go to 'Linker|Command Line' in the SDL Property Pages and remove '/MACHINE:I386' in 'Additional Options'ġ2. Make sure that the checkbox in the build column is checked for both solutionsġ1. For Project SDLmain click on the drop-down menu under 'Platform' and select “”., select New platform: 圆4 with Copy settings from: win32 and un-check 'Create new solutions platform'ĩ. Name it SDLmain_圆4, copy settings from Release and make sure 'Create new solution configurations' is checkedĨ. For Project SDLmain go to the drop-down menu under 'Configuration' and select “”. Click on the drop-down menu under 'Platform' and select “”., select New platform: 圆4 with Copy settings from: win32 and check 'Create new solutions platform'ħ. Name it SDL_圆4, copy settings from Release and make sure 'Create new solution configurations' is checkedĦ. For Project SDL go to the drop-down menu under 'Configuration' and select “”. Right-click on the SDL project, open 'Properties' window and open 'Configuration Manager'ĥ. Tar zxvf binutils-2.20. Python 2.6ĭownload and install python-2.6.5.amd64.msiĢ. ![]() ![]() VirtualBox 3.2.4 - VirtualBox-3.2.2Ĭode: Select all tar zxvf QT 4.6.2 - qt-everywhere-opensource-src-4.6.2.zipĬygwin 1.7.5 with devel packages binutils, bison, flex, gcc-core, gettext, libgcc1, libssp0, libstdc++6, libxml2, make Microsoft Windows Driver Development Kit – 3790.1830 (outdated but can still be obtained through ) OS: Windows XP Professional 圆4 Edition Version 2003 Service Pack 1 Thanks to keros, pessimism, yk70010 and Ben Zhu. I'll update the links in post #1 to refer to those links - thanks for finding them.Build instructions for VirtualBox OSE 3.4.2 on 64-bit Windows below. ![]() The 64-bit version of 5.16.3 you reference at CNet is identical to the one I have, which came from ActiveState's site. I'm not going to post the binaries as this might violate some ActiveState terms. Reinstalling 5.16 works fine, so I'd say the only option currently is that version. Version 5.18 does not have certain required modules available, so that's a no-go. Given the unfriendliness here towards anything not JScript or VBScript, I'm not hopeful this will get investigated or resolved. The 32-bit version of ActivePerl 5.20 causes DirectoryOpus to emit to the log the diagnostic "Script Engine 'perlscript' could not be opened". The 64-bit version of ActivePerl 5.20 causes DirectoryOpus 11.12.04 to crash upon selecting a perlscript rename script. there is a download-location on the forum somewhere where you can store 'your'ĪctivePerl? But likely that requires okay from the administrator. Maybe you can verify the checksums? Alternatively, maybe. Now, I don't know which versions you have available at yours. for 圆4 one might try it from CNet - ActiveState ActivePerl Windows (64-bit)ĭ/ActiveState-Ac. I am not sure whether the below files are 'reworked' (meaning: added trojans, malware, pups whatever)īut. If that is the case, then the below can be ignored. So, the latest version of Dynamic Renamer is indeed compatible with v5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |