C / C++ / MFC

19-Sep-02 23:19

Hello Stephane,

Thanks for useful reply Smile | :)

My month article: Game programming by DirectX by Lan Mader.
Please visit in: www.geocities.com/hadi_rezaie/index.html

Hadi Rezaie

Thread problem !

Hadi Rezaee19-Sep-02 21:53

19-Sep-02 21:53

Hello there ...
What's wrong in below code ?

void CTestthreadDlg::OnStart()
{
DWORD dwThreadID, dwThreadParam = 1;

hThread = ::CreateThread( NULL, 0, ThreadFunc, &dwThreadParam, 0, &dwThreadID );
}

DWORD WINAPI CTestthreadDlg::ThreadFunc(LPVOID lpParam)
{
m_List.AddString( "I wanna die, die for you ... Cause i know you are my only one" ); // Poke tongue | ;-P

return 0;
}

Compiler show me this error:

E:\Microsoft Visual Studio\MyProjects\testthread\testthreadDlg.cpp(102) : error C2664: 'CreateThread' : cannot convert parameter 3 from 'unsigned long (void *)' to 'unsigned long (__stdcall *)(void *)'
None of the functions with this name in scope match the target type

My month article: Game programming by DirectX by Lan Mader.
Please visit in: www.geocities.com/hadi_rezaie/index.html

Hadi Rezaie

Nish Nishant19-Sep-02 22:16

Nish Nishant

19-Sep-02 22:16

Make your thread-proc function static

Nish

Author of the romantic comedy

Summer Love and Some more Cricket [New Win]

Review by Shog⁹
Click here for review[NW]

Hadi Rezaee19-Sep-02 22:34

19-Sep-02 22:34

Well, now my source code works fine by declaring ThreadFunc as global !

Cup, can you show me how declare ThreadFunc as static function ?

My month article: Game programming by DirectX by Lan Mader.
Please visit in: www.geocities.com/hadi_rezaie/index.html

Hadi Rezaie

Nish Nishant19-Sep-02 22:42

Nish Nishant

19-Sep-02 22:42

Hadi_Rezaie wrote:
Cup, can you show me how declare ThreadFunc as static function ?

Hmmmm! No one's ever called me "cup" before Smile | :)

Anyway making a member function static is easy. Just add static to the function declaration.

For example :-

static int GetTotal();

Regards,
Nish

Author of the romantic comedy

Summer Love and Some more Cricket [New Win]

Review by Shog⁹
Click here for review[NW]

Hadi Rezaee19-Sep-02 22:45

19-Sep-02 22:45

Hello dear Nishant S Rose | [Rose]

I'm so sorry about my wrong in typing your name ...
It's because i asked this question in two message board, cup is the name of he ...

And i want to thank you for all helps Wink | ;)

With Best Regards

My month article: Game programming by DirectX by Lan Mader.
Please visit in: www.geocities.com/hadi_rezaie/index.html

Hadi Rezaie

Hans Ruck19-Sep-02 22:14

Hans Ruck

19-Sep-02 22:14

I think the method ThreadFunc should be declared as static.
Or you can use an ordinary function, not a method. This, i think, is the best choice because it always keeps you away from the attempt of using static/non static members in a static method.

rechi

Arjan Schouten19-Sep-02 22:14

Arjan Schouten

19-Sep-02 22:14

If I recall correct you have to declare your ThreadFunc static if you want it to be a member function. Or you can declare it global.

In cpp file

DWORD WINAPI ThreadFunc(LPVOID lpParam); //Global declaration<br />
<br />
DWORD WINAPI ThreadFunc(LPVOID lpParam)<br />
{<br />
    DoStuff();<br />
}<br />
<br />
van Padoea<br />

Hadi Rezaee19-Sep-02 22:32

19-Sep-02 22:32

Thanks, it works fine Big Grin | :-D

My month article: Game programming by DirectX by Lan Mader.
Please visit in: www.geocities.com/hadi_rezaie/index.html

Hadi Rezaie

Hadi Rezaee19-Sep-02 22:35

19-Sep-02 22:35

Arjan Schouten19-Sep-02 22:44

Arjan Schouten

19-Sep-02 22:44

In *.h

static UINT ThreadFunc(LPVOID lParam);

In *.cpp

UINT MyClass::ThreadFunc(LPVOID lParam)<br />
{<br />
}

van Padoea

Hadi Rezaee19-Sep-02 22:47

MFC DLLs and Ms Visual Studio Installer

19-Sep-02 22:47

Hello van Padoea,

Your help is very USEFULL, thank you Smile | :)

My month article: Game programming by DirectX by Lan Mader.
Please visit in: www.geocities.com/hadi_rezaie/index.html

Hadi Rezaie

Mirko M.19-Sep-02 21:29

Mirko M.

19-Sep-02 21:29

I need to create project in VSI that
automatically installs MFC DLLs and my
application.

How must I set the following properties
for the MFC DLLs (MFC42D.DLL, MFCD42D.DLL,
MFCO42D.DLL, MSVCTRD.DLL)??

- Condition
- DoNotIninstall
- Folder
- Hidden
- ReadOnly
- Register
- SharedLegacyFile
- System
- Transitive
- Vital

Thank you very much.

Steve S19-Sep-02 21:50

Steve S

19-Sep-02 21:50

You shouldn't be doing this. Those are all debug DLLs and according to the VC++ license, they are not redistributable.

You should only ship release build binaries, and you probably don't need to ship the MFC DLLs for those, since the first three you name are all rolled into MFC42.DLL, which is present on a lot of machines anyway, unless you have a big Win95 market.

The MSVCRT.DLL is also there, otherwise a lot of MS apps would break. Big Grin | :-D

Steve S
[This signature space available for rent]

Mirko M.19-Sep-02 22:08

Mirko M.

19-Sep-02 22:08

So, if I have well understood, I do not
need to install any DLL.
The only ones needed are MFC42.DLL and
MSVCRTD.DLL that are installed in all machines
with the OS.

Do you think that my installer must try
to install them in order to avoid problems ?
Or also them are not redistributable ?
If I can (or must) try to install them, which
properties have I to set ?

The problem is that my application is very
critical and there must be none problem for
its installation.

Steve S19-Sep-02 22:17

Steve S

19-Sep-02 22:17

In that case, why not build them with minimal dependencies, by specifying that you want to link statically to MFC and the CRT library?

Steve S
[This signature space available for rent]

Mirko M.19-Sep-02 22:44

Mirko M.

19-Sep-02 22:44

That could be a solution. Anyway we have to distribute other files
as, in example, MsFlexGrid.ocx. We have think to dinamically
link DLLs also to minimize the amount of load memory if more than
one application is launched in the same time. So we'd prefer to follow
this way if it is possible.
Anyway,we have not considered license problems so we would like to
examine it.

What do you think about ?
Where can we find some docs ?
Any other problems ??

Stephane Rodriguez.19-Sep-02 23:07

Stephane Rodriguez.

19-Sep-02 23:07

First of all MFC42.DLL, ..., is not part of the operating system. You cannot assume the DLLs are installed. And you cannot assume the right MFC42.DLL version is installed (which is 4.21 for VC++5.0, and 6.0 for VC++6.0).

MSVCRTD.DLL is a debug build, something you don't distribute. I guess you are talking about MSVCRT.DLL.

To know the DLLs that you need to distribute, you can use "dependency walker" (Visual studio tool directory). Beware that's a static listing, it does not show dynamically loaded DLLs.

MS requires you to build a .msi package (or your program will not install on Windows XP depending on user profile). This package references Merge Modules (*.msm files), and there is a merge module for the MFC run-time DLLs provided with the VS.NET cd. See redist.txt file in the cd.
I guess you can download the merge module from the MS site too. (don't know the url).

MS quote (http://www.microsoft.com/ddk) : As of September 30, 2002, the Microsoft® Windows® 2000 DDK, the Microsoft Windows 98 DDK, and the Microsoft Windows NT® 4.0 DDK will no longer be available for purchase or download on this site.

Mirko M.19-Sep-02 23:29

Mirko M.

19-Sep-02 23:29

I have found mfc42.dll and msvcrt.dll in the
REDIST.TXT file among "REDISTRIBUTABLE CODE - Extended Use"
files.
So, can I assume that I can deliver them without problems ??

I have also found mfc42.msm and msvcrt.msm in the following position:
"C:\Programmi\Microsoft Visual Studio\Common\Tools\VSInst\BuildRes"

can I use them ??
And how ??

As you can see, I not skilled and I need Help !!!

Thanks a lot.

Stephane Rodriguez.19-Sep-02 23:44

Stephane Rodriguez.

19-Sep-02 23:44

You are using VC++ 6.0, right ?

VC.NET has better .msi support, but with VC++ 6.0 you must rely on InstallShield 7 to build your setup.

Of course, if you are distributing a shareware, you may just play on the low side and distribute a simple zip file with both your .exes and .dlls and the MFC dlls in the SAME directory (you can test for yourself, it works).

If you are working on a real world software project, then I guess the company you work for must pay a lot of attention to the Deployment part.

You have plenty of documents to read on MSDN : download the Windows Installer SDK from the MS site...