<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<meta charset="utf-8">
<p style="color: rgb(0, 0, 0); font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><br>
"Hello,
I noticed on vm-dev, that you updated the vm compiling process to
gcc-4. Because there are no updates to the cog svn, I assume that
those changes are for the standard stack vm, but not cog. Is this
right? And what would need to change to be able to compile cog
with mingw gcc 4? Given the updates to the stack vm repository,
are they (easily?) adaptable to cog, given some hours of fighting
with the compiler, or have those projects diverged to far?
When creating sources using the most recent versions of Squeak,
VMMaker.oscog and Cog, I always end up with a compiler error in
ADPCMCodecPlugin.c. If I use instead that file from the cog svn,
there are no errors. How is the file in the repository generated?
So far, generating the sources using the SqueakCogVM
configuration, I changed the URIs in that method. What is the
proper way to configure where I checked out the sources? (Telling
FileDirectory>>#pathFromURI: to substitute 'oscogvm' by the
correct path, I guess.)
Thank you,
Lars"<br>
<br>
Hi Lars, <br>
<br>
This list looks pretty dead. You're better off asking on the main
vm-dev list. The question of up-to-date sources is a little
complicated for Cog. svn is not your best destination, I'd say.
Perhaps gitorious. <br>
</p>
<p style="color: rgb(0, 0, 0); font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><a class="moz-txt-link-freetext" href="https://gitorious.org/~estebanlm">https://gitorious.org/~estebanlm</a><br>
</p>
<p style="color: rgb(0, 0, 0); font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">You
can follow links from there to other Cog developers like Igor. <br>
</p>
<p style="color: rgb(0, 0, 0); font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">The
easiest thing to do about the plugin that won't compile
(ADPCMCodecPlugin.c) is to remove it before compiling. I don't
recall how to do that with CMakeVMMaker. That would be a
straightforward question to ask on vm-dev, though. <br>
</p>
<p style="color: rgb(0, 0, 0); font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal; line-height:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Chris
<br>
</p>
</body>
</html>