LINK : fatal error LNK1181: cannot open input
file'Files\pd\bin;\msvc\Build;\win32_vcpp\Build;\objs /DLL /MANIFEST /MANIFESTFILE:d:\Gem-do-2\build\win-vs2008\Debug\Gem.dll.intermediate.manifest /MANIFESTUAC:level='asInvoker'.obj'
my building environment not right?
dunno, but the "Files\pd" indicates that "C:\Program Files\pd" was split at the space.
anyhow, would you mind building "Release"? that's the configuration i
use when building (and which i used to build 3 days ago)
sure. by Release you mean the 93.3.(?) i took it from the Gem page. the date is 20111110.
upgraded the vs2003 to 2008 build only GEM: "LNK1104 cannot open file "libjpeg.lib"
probably this should be in Gemlibs which is not part of the package. the notes i found about Gemlibs did not point to a 'solution'.
a link on the page: "what libraries does GEM use?" to simtel.net takes forever to respond at a download request.
sorry if it starts to be annoying, but i really would appreciate a good ending of this efforts.
rolf
On 01/28/12 18:15, rolf meesters wrote:
sure. by Release you mean the 93.3.(?)
no. using master should be fine.
with "Release" i mean the configuration flavour (somewhere in the top line of MSVC you can select between "Release", "Debug" and "ReleaseDummy". you seem to have chosen "Debug" - simply choose "Release" and recompile)
fgmfdafr IOhannes
after going back and forth a few times, using "release" instead of "debug" in MSVC i can produce a build only of GEM without an error. i now have a.o. gem.dll. what to do next, just copy & replace in the installed Pd?
(of course i tried already: "gem.dll couldn't load")
btw isn't the imegjpeg plugin also needed for working with .jpg files?
rolf
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-01-30 19:51, rolf meesters wrote:
after going back and forth a few times, using "release" instead of "debug" in MSVC i can produce a build only of GEM without an error. i now have a.o. gem.dll.
cool
what to do next, just copy & replace in the installed Pd?
for instance. you could also try to point Pd'd path to the location of the new Gem.dll (make sure to add it before the path to the old Gem) or open cmd, cd into the build directory and run pd.com from there.
(of course i tried already: "gem.dll couldn't load")
run with "-verbose" and see whether it searches at the right place. is there some other output? also try to run pd.com from cmd, and see whether something interesting is printed to the console.
btw isn't the imegjpeg plugin also needed for working with .jpg files?
obviously. you should try to run the gem_imageJPEG.dll from the release besides the new Gem.dll
unfortunately i noticed that the plugins are compiled with SSE2 enabled as well. but since they don't use any SSE2 specific code (so the binaries will only contain SSE2 code autogenerated by the compiler), i hope that they will still be runnable under a PIII. if not, i will have to start a compilation myself :-(
fgmadr IOhannes
what to do next, just copy & replace in the installed Pd?
for instance. you could also try to point Pd'd path to the location of the new Gem.dll (make sure to add it before the path to the old Gem) or open cmd, cd into the build directory and run pd.com from there.
(of course i tried already: "gem.dll couldn't load")
run with "-verbose" and see whether it searches at the right place. is there some other output? also try to run pd.com from cmd, and see whether something interesting is printed to the console.
the loader finds the gem.dll alright, but the next line it says: "couldn't load", nothing more. seems it finds something wrong with the dll. to test i replaced the 'original' dll in pd/extra/Gem with the build one. i tried on different machines, different Pd's (42.5 & 43.1). did build from git.../pd-gem/Gem and also from the release of 93.3. always the same result. (building is done on a P4)
btw isn't the imegjpeg plugin also needed for working with .jpg files?
obviously. you should try to run the gem_imageJPEG.dll from the release besides the new Gem.dll
unfortunately i noticed that the plugins are compiled with SSE2 enabled as well. but since they don't use any SSE2 specific code (so the binaries will only contain SSE2 code autogenerated by the compiler), i hope that they will still be runnable under a PIII.
if not, i will have to start a compilation myself :-(
if it's only about me and the GEM patch i'm trying to run on the PIII's: i just saw: by accident on one of the PIII's i have PdX-42.5 with Gem 92.3 compiled for SSE2. the patch works with jpg files. half of it goes well. what doesn't is a pix_alpha which creates a partly transparent window inside the GEM-window, like a frame around a picture. i'm thinking about a work-around for that. i'll let you know as soon as i have it. then there's no urgency for a SSE2-less Windows version.
thanks sofar rolf
-
IOhannes m zmoelnig -
IOhannes m zmölnig
-
rolf meesters