Trying to reuse code with a static library - C / C++ / MFC Discussion Boards

Richard MacCutchan11-Dec-13 0:23

11-Dec-13 0:23

I would suggest you go to the articles section here[^] and look for articles on the subjects that you need to learn. You can also use Google for wider searches.

Veni, vidi, abiit domum

Re: app for windows 8.1

Erudite_Eric11-Dec-13 1:57

Erudite_Eric

11-Dec-13 1:57

tell your boss to hire someone who can.

Get rid of STL warnings

_Flaviu10-Dec-13 21:58

_Flaviu

10-Dec-13 21:58

I had compiled MFC Grid control 2.27[^] project, but I get a lot of warnings (I use VC6):

C++

GridCell.cpp
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\xmemory(39) : warning C4100: '_P' : unreferenced formal parameter
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\xmemory(41) : warning C4100: '_P' : unreferenced formal parameter
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\vector(249) : warning C4663: C++ language change: to explicitly specialize class template 'vector' use the following syntax:
        template<> class vector<bool,class std::allocator<unsigned int> > ...
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\vector(156) : warning C4018: '<' : signed/unsigned mismatch
        C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\vector(156) : while compiling class-template member function 'void __thiscall std::vector<unsigned int,class std::allocator<unsigned int> >::insert(unsigned int *,unsigned int,const unsig
ned int &)'
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\vector(167) : warning C4018: '<' : signed/unsigned mismatch
        C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\vector(156) : while compiling class-template member function 'void __thiscall std::vector<unsigned int,class std::allocator<unsigned int> >::insert(unsigned int *,unsigned int,const unsig
ned int &)'
C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\xmemory(37) : warning C4100: '_P' : unreferenced formal parameter
        C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\xmemory(68) : see reference to function template instantiation 'void __cdecl std::_Destroy(unsigned int *)' being compiled

and so on ... I had tried
#pragma warning(disable 4100) ... doesn't have any affect ...

How can I get rid of this warnings ? Thank you.

Re: Get rid of STL warnings

Richard MacCutchan10-Dec-13 22:23

Richard MacCutchan

10-Dec-13 22:23

Looking at thos messages suggests that you are using a very old version of Visual Studio. You probably need to upgrade to a later version.

Veni, vidi, abiit domum

Re: Get rid of STL warnings

Freak3010-Dec-13 23:01

Freak30

10-Dec-13 23:01

You could either set the warning level for the whole project to 3 in the settings.

Or you can include the line
#pragma warning(disable 4100)
in you Stdafx.h file before the relevant includes.

Or if you don't want to do this, you can wrap the MFC includes in the following:
#pragma warning (push, 3)
#include "whatever"
#pragma warning (pop)

The good thing about pessimism is, that you are always either right or pleasently surprised.

Re: Get rid of STL warnings

_Flaviu11-Dec-13 2:37

_Flaviu

11-Dec-13 2:37

I had tried to put

C++

#pragma warning(disable 4100)

in stdafx.h, but doesn't work ... I'll try other one ...

Re: Get rid of STL warnings

David Crow11-Dec-13 5:19

David Crow

11-Dec-13 5:19

I seem to recall a yvals.h file. Try here for starters.

"One man's wage rise is another man's price increase." - Harold Wilson

"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous

Trying to reuse code with a static library

Richard Andrew x648-Dec-13 19:21

Richard Andrew x64

8-Dec-13 19:21

I'm trying to put reusable code into a static library and link it into a couple of different projects.

The problem is that while linking one of the projects that's supposed to use the reusable code, it reports all sorts of multiply defined symbols. (See below)

The main projects use DLL versions of the C-runtime, and the static library is set to use the multi-threaded dll version also.

What's the trick to successfully linking a static library into multiple projects?
(If I haven't provided enough info, just ask.)

Multiply defined symbols messages:
(Is this happening because the C-runtime is linked into the static lib first, and then those symbols are conflicting with the symbols in the main project?)

5>LIBCMTD.lib(dbgheap.obj) : error LNK2005: __CrtSetCheckCount already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(dbgheap.obj) : error LNK2005: __calloc_dbg already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(invarg.obj) : error LNK2005: __invoke_watson already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(sprintf.obj) : error LNK2005: _sprintf already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(dbghook.obj) : error LNK2005: __crt_debugger_hook already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(crt0dat.obj) : error LNK2005: __amsg_exit already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(crt0dat.obj) : error LNK2005: __cexit already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(crt0dat.obj) : error LNK2005: __exit already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(crt0dat.obj) : error LNK2005: __initterm_e already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(crt0dat.obj) : error LNK2005: _exit already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(wsetloca.obj) : error LNK2005: __configthreadlocale already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(swprintf.obj) : error LNK2005: _swprintf_s already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(mlock.obj) : error LNK2005: __lock already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(mlock.obj) : error LNK2005: __unlock already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(winapisupp.obj) : error LNK2005: ___crtGetShowWindowMode already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(winapisupp.obj) : error LNK2005: ___crtSetUnhandledExceptionFilter already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(winapisupp.obj) : error LNK2005: ___crtTerminateProcess already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(winapisupp.obj) : error LNK2005: ___crtUnhandledException already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(winxfltr.obj) : error LNK2005: __XcptFilter already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(vsnprnc.obj) : error LNK2005: __vsnprintf_s already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(hooks.obj) : error LNK2005: "void __cdecl terminate(void)" (?terminate@@YAXXZ) already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(crt0init.obj) : error LNK2005: ___xi_a already defined in msvcrtd.lib(cinitexe.obj)
5>LIBCMTD.lib(crt0init.obj) : error LNK2005: ___xi_z already defined in msvcrtd.lib(cinitexe.obj)
5>LIBCMTD.lib(crt0init.obj) : error LNK2005: ___xc_a already defined in msvcrtd.lib(cinitexe.obj)
5>LIBCMTD.lib(crt0init.obj) : error LNK2005: ___xc_z already defined in msvcrtd.lib(cinitexe.obj)
5>LIBCMTD.lib(vswprnc.obj) : error LNK2005: __vsnwprintf_s already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(dbgrptw.obj) : error LNK2005: __CrtDbgReportW already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(printf.obj) : error LNK2005: _printf already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(errmode.obj) : error LNK2005: ___set_app_type already defined in msvcrtd.lib(MSVCR120D.dll)
5>LIBCMTD.lib(towlower.obj) : error LNK2005: _towlower already defined in msvcrtd.lib(MSVCR120D.dll)
5>LINK : warning LNK4098: defaultlib 'msvcrtd.lib' conflicts with use of other libs; use /NODEFAULTLIB:library
5>LINK : warning LNK4098: defaultlib 'LIBCMTD' conflicts with use of other libs; use /NODEFAULTLIB:library

The difficult we do right away...
...the impossible takes slightly longer.

Re: Trying to reuse code with a static library

Richard MacCutchan8-Dec-13 22:24

Richard MacCutchan

8-Dec-13 22:24

See http://stackoverflow.com/questions/925540/how-to-resolve-the-following-linker-errors-in-visual-studio[^].

Veni, vidi, abiit domum

Re: Trying to reuse code with a static library

Albert Holguin9-Dec-13 5:23

Albert Holguin

9-Dec-13 5:23

This looks like you're mixing C runtime library types, double check your settings and make sure they're the same. MS really makes it a pain to use libraries that support different projects (that may have multiple runtimes). Essentially you're supposed to make a lib build compatible with each runtime available and link up your main project to the right one.

Re: Trying to reuse code with a static library

Richard Andrew x649-Dec-13 6:35

Richard Andrew x64

9-Dec-13 6:35

Thank you, you are correct. It turns out that it had to do with a third-party library that I was also linking in. I was linking in the version that used the static C library instead of the shared.

The difficult we do right away...
...the impossible takes slightly longer.

Re: Trying to reuse code with a static library

Albert Holguin9-Dec-13 6:43

Albert Holguin

9-Dec-13 6:43

Glad you found the cause... Smile | :)

Re: Trying to reuse code with a static library

Gisle Vanem9-Dec-13 22:59

Gisle Vanem

9-Dec-13 22:59

Add the option '-verbose' to the linker. It will tell you exactly why it pulls in which lib.
Maybe also add '-nodefaultlib:libcmtd.lib' to force 'link' not to pull in

libcmtd.lib<code>.<br />
<div class="signature">Gisle V. <br />
<br><small><tt># rm -vf /bin/laden<br />
/bin/rm: success</tt></small><br></div>

Missing Button Click Message

BarryPearlman8-Dec-13 8:50

BarryPearlman

8-Dec-13 8:50

The objective is to create a class that contains the methods to create and gather messages from a series of message dialogs by means of a series of buttons on a dialog created with the resource editor.

The app is being written with VS 2010 and the classes, events etc. utilizing the supplied Wizards. This is an SDI app with p_MFCls-> pointing to the MainFrameEx* object and p->MsgCls being the child of p_MFCls-> and a CWnd* object. p_Dlg-> is a pointer to the actual dialog box and is a CDialog* object parented by the p_MsgCls object.

FWIW: Windows 8.1

I have the following code (partial):

In p_MFCls:
//.h

CJBK_Msg*         p_MsgCls;

//.cpp

p_MsgCls = new CJBK_Msg;
      ASSERT(p_MsgCls->Create(NULL, NULL, 0, CRect(0, 0, 0, 0), this, IDCls_Msg));

In p_MsgCls, when the appropriate message is received, we have:

//.h
CDialog*      p_DlgBox;

//.cpp
<pre lang="cs">p_DlgBox = new CDialog;
      ASSERT(p_DlgBox->Create(p_strMsgBox->nDlgBoxResID, this));

For the button(s), I used the Event Handler Wizard but whether I tell it to send the event to p_MFCls or p_MsgCls, it never gets there when I click the button control.

Can anyone spot something that I have missed?

Thanks and Happy Holidays to all,

Barry

Re: Missing Button Click Message

Richard MacCutchan8-Dec-13 22:21

Richard MacCutchan

8-Dec-13 22:21

BarryPearlman wrote:
Can anyone spot something that I have missed?

Where is the actual event handling code? What you have shown above does not tell us anything about where these events are supposed to be captured.

Veni, vidi, abiit domum

Re: Missing Button Click Message

BarryPearlman9-Dec-13 3:45

BarryPearlman

9-Dec-13 3:45

Sorry about that! Ideally the button click event should be handled first in p_MsgCls since p_MsgCls-> is intended to handle all of the messages for the entire application. Second choice is CMainFrameEx.

Using the Event Handler Wizard for p_MsgCls I get:

//.h

DECLARE_MESSAGE_MAP()
public:

afx_msg void OnBnClicked_MB_Btn2();

//.cpp

BEGIN_MESSAGE_MAP(CJBK_Msg, CWnd)

                ..........................

  ON_BN_CLICKED(ID_MB_Btn_2, &CJBK_Msg::OnBnClicked_MB_Btn2)
END_MESSAGE_MAP()

void CJBK_Msg::OnBnClicked_MB_Btn2()
{
  // TODO: Add your control notification handler code here
}

I am working under the assumption that if the Event Handler Wizard (in general) presents me with a choice, it is a valid one and will work.

Thanks,

Barry

Re: Missing Button Click Message

Richard MacCutchan9-Dec-13 3:54

Richard MacCutchan

9-Dec-13 3:54

BarryPearlman wrote:
I am working under the assumption

Never do that, check everything. However good the wizards may be they are not infallible. You can easily check that things are plugged together correctly by setting a few breakpoints in your code and running some controlled tests.

Veni, vidi, abiit domum

Re: Missing Button Click Message

BarryPearlman9-Dec-13 4:08

BarryPearlman

9-Dec-13 4:08

I always do. That is how I found out that the code that the Event Wizard Handler was writing code that wasn't working in the first place. The question still remains why can't I get the event to fire in p_MSCls->?

Thanks,

Barry

Re: Missing Button Click Message

Richard MacCutchan9-Dec-13 5:12

Richard MacCutchan

9-Dec-13 5:12

Does the control that raises the event belong to this class, and are the message macros pointing to the right places? From the little pieces of code you have shown us it is not easy to understand how your project fits together.

Veni, vidi, abiit domum

Re: Missing Button Click Message

BarryPearlman9-Dec-13 9:27

BarryPearlman

9-Dec-13 9:27

You may be on the right class concerning who belongs to which class and hence the missing events. I will get back to this project later on in the week and thanks to you have some new avenues to explore.

Thanks & Happy Holidays,

Barry

Re: Missing Button Click Message

Freak309-Dec-13 1:18

Freak30

9-Dec-13 1:18

You have wrapped the Create() functions in ASSERT() macros, which at least in Visual Studio 6.0 means they are executed only in debug mode. Assuming this behavior has not changed in VS 2010, you should use VERIFY() instead.

The good thing about pessimism is, that you are always either right or pleasently surprised.

Re: Missing Button Click Message

BarryPearlman9-Dec-13 4:02

BarryPearlman

9-Dec-13 4:02

This post dealt with missing events, not a request for the difference between ASSERT() and VERIFY()! Frankly, I am hard pressed to find a decent explanation of the fine nuances between them, except their use during runtime and debug.

It is my own personal philosophy that the end user should never see the arcane messages these macros produce. An error at a hex address means absolutely nothing to a user except that there is an error and that the developer has failed to take something into account.

Perhaps a philosophical dissertation/lecture is in order here??

Re: Missing Button Click Message

Freak3010-Dec-13 22:51

Freak30

10-Dec-13 22:51

This wasn't meant as a philosophical discussion. If you enclose an important function call, e.g. the creation of a dialog in an ASSERT(), the dialog will not be created in Release mode and therefore can't receive any messages.

If you use VERIFY(), the dialog will be created in Release mode as well. However, the "arcance message" as you call it, will only be displayed in Debug mode.

The good thing about pessimism is, that you are always either right or pleasently surprised.

Morse code in Cpp

Dhananjay RajeNimbalkar6-Dec-13 23:16

Dhananjay RajeNimbalkar

6-Dec-13 23:16

I'm doing project on morse code translator in Cpp Im unable to write it?? plz help ....

Re: Morse code in Cpp

Richard MacCutchan7-Dec-13 1:18

Richard MacCutchan

7-Dec-13 1:18

Help with what? Please don't expect people here to do your work for you.

Veni, vidi, abiit domum

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.