Why say it's not supported if there is a build file for it? OK,
ok, so support is more than just providing a build file. But if
it builds with that environment and there are build files already
created and being submitted for it, then why not either include them in
the over-all project or at least provide information on the developer's
website that includes information on where those files can be
acquired. Knowing that there was a functioning nmake-compatible
build file for MS C++ 2003 toolkit would have made my life about 100x
easier this past summer while I was trying to build a program with
Sword integration that might have succeeded (and hopefully will once I
get home in December) if I had been able to locate an nmake file.<br>
<br>
--Greg<br><br><div><span class="gmail_quote">On 10/11/05, <b class="gmail_sendername">Chris Little</b> <<a href="mailto:chrislit@crosswire.org">chrislit@crosswire.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>Lynn Allan wrote:<br>> Here is a link to a patch for the project files in vcppmake\vc6 and<br>> vcppmake\vc7.1 that reference papyriplain.cpp and papyriplain.h<br>> <a href="http://lcdbible.sourceforge.net/misc/libsword_papyriplain_vc6_vc71.patch">
http://lcdbible.sourceforge.net/misc/libsword_papyriplain_vc6_vc71.patch</a><br>><br>> Also, "while you are at it" ...<br>><br>> I would appreciate having project files in svn for vc8 (Microsoft 2005
<br>> beta-2 compiler) and the nmake file for the C++ 2003 free non-ide<br>> toolkit. These are zipped in:<br>> <a href="http://lcdbible.sourceforge.net/misc/vcppmake_vc8_toolkit.zip">http://lcdbible.sourceforge.net/misc/vcppmake_vc8_toolkit.zip
</a><br>><br>> and unzips to go in lib:<br>> lib<br>> ...vcppmake<br>> ......Cpp2003Toolkit\libsword.mak<br>> ......vc8\libsword.sln<br>> ......vc8\libsword.vproj<br><br>Is there something novel about the VC8 project files that requires their
<br>inclusion in SVN (as opposed to allowing the IDE to update the project<br>files to the new format)? More project files mean we have more to<br>maintain, something to be avoided if possible. I think the facts that<br>MSVC 8 isn't yet released and isn't yet one of the environments we
<br>support suggest we ought to hold off on including VC8 files for now.<br><br>--Chris<br><br>_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org
</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br>