From: "Dave Yeo" <cwmm-dev@2rosenthals.com>
Subject: Re: [cwmm-dev] Compiling cwwm
To: CWMM Developers Mailing List <cwmm-dev@2rosenthals.com>
References: <list-934924@2rosenthals.com>
Message-ID: <918a19fd-3006-e759-ed08-3fa596e0dd9c@gmail.com>
Date: Tue, 28 Jul 2020 23:26:05 -0700
User-Agent: Mozilla/5.0 (OS/2; Warp 4.5; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <list-934924@2rosenthals.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 07/28/20 10:37 PM, Steven Levine wrote:
> In <list-934926@2rosenthals.com>, on 07/28/20
>    at 10:09 PM, "Dave Yeo" <cwmm-dev@2rosenthals.com> said:
>
> Hi,
>
>> Well, at least mediafolder.hh and progfolder.hh seem to be hand written
>> judging by their head, GPL rather then a notice about when and how
>> generated.
>
> The docs say this is OK.  BTW, did you happen to notice the icc /Fs
> option?

No.

>
> Also while setting up to replicate your dde4cpe trap, I noticed a missing
> #endif at:
>
> mediafolder.hh:325
> #if 0
>   virtual MRESULT wpDrop(HWND hwndCnr,PDRAGINFO pDragInfo,PDRAGITEM
> pDragItem);
>   virtual BOOL cwClose();
>   virtual BOOL wpSetupOnce(PSZ pSetupString);
>   virtual BOOL wpSetup(PSZ pSetupString);
> #endif // 2020-07-28 SHL was missing

Sure we're using the same mediafolder.hh? That would be line #322 here 
and quickly reviewing, it looks like the #endif is at 341. Might have 
missed a #if though.

>
>> Hmm, seems that FILTERFLAGS that I've been chasing is Warp V4 and newer,
>> which probably explains why I can't get rid of it without introducing a
>> lot more errors.
>
> Hmmm. :-)
>
>> 3.74.1 to compile. Haven't noticed any make problems but I guess I
>> should start over with the hh files using the ones included with VAC++
>> 3.08.
>
> I'm not so sure this is the way to go.  I rarely believe everything I read
> when it does not seem to make sense.  Chris was obviously using the
> toolkit headers such as os2.h.  I find it hard to belive he was not using
> the SOM header from the toolkit too.
>

Why? os2.h and the SOM headers are included with VAC++ 3.08 here (found 
on Winworld IIRC) and the mediafolder/include/wpobject.hh has,
// This file was generated by the IBM "DirectToSOM" emitter for C++ (V1.77)
// Generated at 10/22/96 06:18:53 EDT
// This is class: WPObject
// Mangled class name: WPObject
// SE: May 19/94

While the toolkit version I compiled has,

// Generated from wpobject.idl at 07/28/20 09:09:35 EDT
// By the IBM DTS C++ header emitter version 1.156
// Using cpp.efw file version 1.87

Hmm, they seem like separate programs rather then different versions of sc.
Anyways, I'll have a go using the idl files included with VAC++ tomorrow 
if not too burned out.
There's also the Warp v3 toolkit on Winworld, looks like floppies though :(
The mediafolder headers in the eCS zip also look interesting.
Dave

-- 
This email was Anti Virus checked by Astaro Security Gateway. http://www.sophos.com