<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Building OS/2 apps from QuickC for Windows	</title>
	<atom:link href="https://virtuallyfun.com/2023/10/23/building-os-2-apps-from-quickc-for-windows/feed/" rel="self" type="application/rss+xml" />
	<link>https://virtuallyfun.com/2023/10/23/building-os-2-apps-from-quickc-for-windows/</link>
	<description>Fun with Virtualization</description>
	<lastBuildDate>Wed, 25 Oct 2023 19:37:56 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.1</generator>
	<item>
		<title>
		By: neozeed		</title>
		<link>https://virtuallyfun.com/2023/10/23/building-os-2-apps-from-quickc-for-windows/comment-page-1/#comment-341716</link>

		<dc:creator><![CDATA[neozeed]]></dc:creator>
		<pubDate>Wed, 25 Oct 2023 19:37:56 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/?p=13382#comment-341716</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://virtuallyfun.com/2023/10/23/building-os-2-apps-from-quickc-for-windows/comment-page-1/#comment-341708&quot;&gt;Malcolm&lt;/a&gt;.

Looking back at the screenshot, I think it linked, it&#039;s the resource compiler being called for no apparent reason that is bombing out.  I should look at the makefile again, but that means getting out of the electric blanket...]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://virtuallyfun.com/2023/10/23/building-os-2-apps-from-quickc-for-windows/comment-page-1/#comment-341708">Malcolm</a>.</p>
<p>Looking back at the screenshot, I think it linked, it&#8217;s the resource compiler being called for no apparent reason that is bombing out.  I should look at the makefile again, but that means getting out of the electric blanket&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Malcolm		</title>
		<link>https://virtuallyfun.com/2023/10/23/building-os-2-apps-from-quickc-for-windows/comment-page-1/#comment-341708</link>

		<dc:creator><![CDATA[Malcolm]]></dc:creator>
		<pubDate>Wed, 25 Oct 2023 18:34:52 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/?p=13382#comment-341708</guid>

					<description><![CDATA[Somewhat related, but for QuickC 2.0 for DOS:

https://jeffpar.github.io/kbarchive/kb/040/Q40503/

I think I figured this out the hard way back in the day, since we didn&#039;t have Internet connections when it was written.  Note that this article is from 1989 so references to &quot;Windows&quot; should be read as &quot;Windows 2.x&quot;.

There&#039;s also this which is for QuickC 2.5:

https://jeffpar.github.io/kbarchive/kb/065/Q65490/

I&#039;ve never seen the disk it refers to.  Looking now link.exe was not included at all with QuickC 2.5, which seems like a big functional regression.  I&#039;m very skeptical of the implication that Link 5.02 in QuickC 2.0 can&#039;t target Windows 3.0.

Googling for the disk turned up https://books.google.com/books?id=FDwEAAAAMBAJ&#038;pg=PP8&#038;lpg=PP8#v=onepage&#038;q&#038;f=false which might be interesting.  Note the &quot;SMK&quot; it refers to is what we&#039;d call &quot;WLO&quot; today.  Interesting that it&#039;s explicitly one-third the cost of the Windows SDK.

AFAICT all of the 5.x linkers can generate either Windows or OS/2 binaries.  Even if they couldn&#039;t, OS/2 includes a version of link.exe and doscalls.lib, so all you need for OS/2 development is a 16 bit OMF compiler.]]></description>
			<content:encoded><![CDATA[<p>Somewhat related, but for QuickC 2.0 for DOS:</p>
<p><a href="https://jeffpar.github.io/kbarchive/kb/040/Q40503/" rel="nofollow ugc">https://jeffpar.github.io/kbarchive/kb/040/Q40503/</a></p>
<p>I think I figured this out the hard way back in the day, since we didn&#8217;t have Internet connections when it was written.  Note that this article is from 1989 so references to &#8220;Windows&#8221; should be read as &#8220;Windows 2.x&#8221;.</p>
<p>There&#8217;s also this which is for QuickC 2.5:</p>
<p><a href="https://jeffpar.github.io/kbarchive/kb/065/Q65490/" rel="nofollow ugc">https://jeffpar.github.io/kbarchive/kb/065/Q65490/</a></p>
<p>I&#8217;ve never seen the disk it refers to.  Looking now link.exe was not included at all with QuickC 2.5, which seems like a big functional regression.  I&#8217;m very skeptical of the implication that Link 5.02 in QuickC 2.0 can&#8217;t target Windows 3.0.</p>
<p>Googling for the disk turned up <a href="https://books.google.com/books?id=FDwEAAAAMBAJ&#038;pg=PP8&#038;lpg=PP8#v=onepage&#038;q&#038;f=false" rel="nofollow ugc">https://books.google.com/books?id=FDwEAAAAMBAJ&#038;pg=PP8&#038;lpg=PP8#v=onepage&#038;q&#038;f=false</a> which might be interesting.  Note the &#8220;SMK&#8221; it refers to is what we&#8217;d call &#8220;WLO&#8221; today.  Interesting that it&#8217;s explicitly one-third the cost of the Windows SDK.</p>
<p>AFAICT all of the 5.x linkers can generate either Windows or OS/2 binaries.  Even if they couldn&#8217;t, OS/2 includes a version of link.exe and doscalls.lib, so all you need for OS/2 development is a 16 bit OMF compiler.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
