Compiling wx Samples in the Borland IDE

From: Francesco Montorsi Date: Sun, 1 Mar 2009 15:02:11 +0000 (+0000) Subject: remove old and outdated tech notes X-Git-Url: https://git.saurik.com/wxWidgets.git/commitdiff_plain/0e40db55850127ae9b18ecf774d5e27b68574bbc?ds=sidebyside remove old and outdated tech notes git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@59240 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- diff --git a/docs/tech/index.txt b/docs/tech/index.txt index 9b81fac4d8..f6aac289e2 100644 --- a/docs/tech/index.txt +++ b/docs/tech/index.txt @@ -4,13 +4,13 @@ tn0001.txt How to add a new sample tn0002.txt wxWidgets translator guide tn0003.txt Adding wxWidgets class documentation -tn0004.htm *** Not currently applicable Compiling a sample in the C++Builder IDE +tn0004.htm *** REMOVED *** (obsoleted by Bakefile changes) tn0005.txt Adding a wxWidgets contribution tn0006.txt *** REMOVED *** (obsoleted by tn0013.txt) -tn0007.txt *** Not currently applicable Using and modifying the BC++ IDE files -tn0008.htm How to learn wxWidgets programming +tn0007.txt *** REMOVED *** (obsoleted by Bakefile changes) +tn0008.htm *** REMOVED *** (included in the manual now) tn0009.htm Creating and converting icons -tn0010.htm Compiling wxWidgets applications in the VC++ IDE +tn0010.htm *** REMOVED *** (obsoleted by Bakefile changes) tn0011.txt All about version numbers tn0012.txt wxWidgets platform, toolkit and library names tn0013.txt How to make a wxGTK distribution diff --git a/docs/tech/tn0004.htm b/docs/tech/tn0004.htm deleted file mode 100644 index b0045ba273..0000000000 --- a/docs/tech/tn0004.htm +++ /dev/null @@ -1,19 +0,0 @@ - - - - - - - Compiling wx Samples in the Borland IDE - - -

-Compiling wxWidgets samples with the Borland CBuilder

-Please use wxWidgets 2.4.x this will not work with the new makefiles in -wxWidgets 2.5.0
-
-
- - diff --git a/docs/tech/tn0007.txt b/docs/tech/tn0007.txt deleted file mode 100644 index bbc063aa41..0000000000 --- a/docs/tech/tn0007.txt +++ /dev/null @@ -1,9 +0,0 @@ -Using and modifying the BC++ IDE files -====================================== - - -Please use wxWidgets 2.4.x - this is not currently supported in wxWidgets 2.6.0 - - - - diff --git a/docs/tech/tn0008.htm b/docs/tech/tn0008.htm deleted file mode 100644 index 196d5bfcbc..0000000000 --- a/docs/tech/tn0008.htm +++ /dev/null @@ -1,144 +0,0 @@ - - - -How to learn wxWidgets programming - - - - - - - - - - - - -

- -How to learn wxWidgets programming - -

- -

- -The following is a response by Edward Ream to a common question, -"What's the best way to learn wxWidgets [and C++]?".

- -Date: Sun, 04 Jun 2000 14:37:06 -0500
-From: "Edward K. Ream"
-To: wx-users@wxwidgets.org
-Subject: Re: [wx-users] How to learn using wx-windows
-Reply-To: wx-users@wxwidgets.org

- -> Reading the Linux Journal article on wxpython, and having used wxclips
-> I got interested in wxwidgets as a development interface. However, the
-> programming experience I got is old, and from a former generation (For-
-> tran). I'd like to refresh my experience and start in C++. Will
-> wx-windows be a very high step to take?

- -I'm new to wxWidgets myself, but I'd like to answer this question -anyway. In the past two years I've learned two similar frameworks -(Apple's Yellow Box, aka NextStep/OpenStep and Borland's C++ -Builder/Delphi) and last year I became a C++ enthusiast after 20 years -of using C.

- -About C++.

- -The major Aha for me was that the complexity of C++ doesn't matter in -practice. What _does_ matter is that C++ allows you to do simple things -simply, more simply than C. With a system like wxWidgets you will be -creating objects and then using those objects to call methods. So don't -be afraid of C++: you'll only be using the easy tip of the -iceberg.

- -Besides the C++ Programming Language, by Bjarne Stroustrup, the -"official" guide to C++, I highly recommend Inside the C++ Object Model, -by Stanley B. Lippman. (Lippman was one of the C++ honchos at Bell -Labs.) This book will tell you what _not_ to do, as well as why -everything in C++ is as it is. If you are confused by anything in C++, -Lippman's book is the cure.

- -About applications frameworks.

- -Application frameworks such as wxWidgets are organized around a set of -cooperating classes. Take a look at the main application class, wxApp, -some frame and panel classes, graphics classes, menu classes, control -classes, etc. In general, to do anything in a framework involves -creating an object of the specified type, then doing something with that -object.

- -For example, suppose you want to create a menu bar. A menu bar is -composed of a single menu bar object of type(class) wxMenuBar that -contains menu objects of type wxMenu. Each menu object contains menu -item objects of type wxMenuItem. So you create the menu bar object, -then create all the menu objects (creating the menu item objects along -the way) and finally "attach" the menu objects to the menu bar object -using a call to the wxMenuBar::Append method.

- -As an overview I would look at the "Alphabetical class reference" -section of the reference manual. I find the HTML version to be the -easiest to use: you can browse very quickly through it. Here's how to -read this (very large) reference:

- -

Get an overview of the kinds of classes involved. The class names -will tell you a lot about what each class does. Open some of the -classes, in particular, wxApp (the main application object), wxFrame, -wxControl (the base class for all controls) and one or two controls, -like wxButton. - -
When scanning a class for the first several times, read the -introductory remarks and quickly scan the list of methods of the class -to get a general idea about what kinds of operations can be done to -objects of the class. You are not looking for detail at this stage, -just for the big picture. In particular, what classes exist and how do -they work together. - -
Pay particular attention to the classes from which a class is -derived. For example, a button (an object of type wxButton) is derived -from the wxControl, wxWindow, wxEvtHandler and wxObject classes. What -does this mean? It means that a button _is_ a control, and a button -_is_ a window, and a button _is_ an event handler and a button _is_ an -object. So you must understand the parent classes of an object to -understand the object itself. - -For example, if b is a button you can invoke b.m for any of method m of -the wxControl, wxWindow, wxEvtHandler or wxObject classes. You are not -limited to just the methods of wxButton! This is one of the keys of -object oriented programming. -

- -Some other tips:

- -Read some sample code. You will find that almost none of the C++ -language is actually being used; it's just endlessly creating objects -and then calling methods using those objects.

- -Learn as much as you can about the String class; after using a good -String class you'll never want to use C's string functions again. -wxWidgets contains other nifty utility classes as well.

- -The application class, wxApp, contains the main event loop. Learn about -event handling and event tables (reading sample code will help). Almost -everything in this kind of application framework happens as the result -of an event and your app is essentially doing nothing but responding to -events. Having the event loop written for you is a major, major -benefit.

- -I hope this helps. Perhaps we can work together in learning about -wxWidgets. Please feel free to ask me any questions you might have. If -I've made any blunders in this posting I hope the wxWidgets experts will -correct me gently.

- -Edward
---------------------------------------------------------------------
-Edward K. Ream email: edream@tds.net
-Leo: Literate Editor with Outlines
-Leo: http://personalpages.tds.net/~edream/front.html
---------------------------------------------------------------------

- - - - - diff --git a/docs/tech/tn0010.htm b/docs/tech/tn0010.htm deleted file mode 100644 index d5470a46fc..0000000000 --- a/docs/tech/tn0010.htm +++ /dev/null @@ -1,212 +0,0 @@ - - - -Compiling wxWidgets applications in the VC++ IDE - - - - - - - - - - - - - -
- -Compiling wxWidgets applications in the VC++ IDE - -
- -

- -

-Settings for wxWidgets 2.2 / Settings for wxWidgets 1.68 - - -

- -To compile wxWidgets samples and applications using the VC++ 5.0 or 6.0 IDE (having compiled wxWidgets -using the makefile or project file provided), the following -steps and settings should be used.

- -

Steps

- -

Create a new WIN32 Application project. -
Add the .cpp and .rc files for your project. -
Apply the settings listed below to the project, replacing c:\wx2 with your wxWidgets -installation path. -

- -

Settings for wxWidgets 2.2

- -These settings apply to wxWidgets 2.1.14 and above but most of them are not -necessary any longer for wxWidgets 2.3+.

- -

General

-The Output files and Intermediate files directory fields should be Debug -for the Debug configuration, and Release for the Release configuration.

- -

Debug: General

-The Executable for debug sessions field should be altered to be the path and name -you'd expect (it may have generated a different name).

- -

C/C++: Preprocessor

-The Preprocessor definitions field should contain the following symbols for Debug:

- -

-WIN32,_DEBUG,_WINDOWS,__WINDOWS__,__WXMSW__,__WXDEBUG__,WXDEBUG=1,
-__WIN32__,WINVER=0x0400,STRICT
-

-and these for Release:

- -

-NDEBUG,WIN32,_WINDOWS,__WINDOWS__,__WXMSW__,__WIN32__,
-WINVER=0x0400,STRICT

-The Additional include directories field should contain the following:

-c:\wx2\include
-

(and of course any other directories you wish to use in your project).

- -

C/C++: Precompiled Headers

- -The Not using precompiled headers or Automatic use of precompiled headers -button should be selected.

- -

C/C++: Code Generation

- -The Use run-time library control should be set to Debug Multithreaded DLL (Debug) -or Multithreaded DLL (Release).

- -

Link: Input

- -The Object/library modules field should contain: - -

-kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib
-ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib comctl32.lib rpcrt4.lib wsock32.lib
-winmm.lib wxmsw25d.lib wxbase25d.lib wxpngd.lib wxzlibd.lib wxjpegd.lib wxtiffd.lib
-

- -for the Debug configuration and - -

-kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib
-ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib comctl32.lib rpcrt4.lib wsock32.lib
-winmm.lib wxmsw25.lib wxbase25.lib wxpng.lib wxzlib.lib wxjpeg.lib wxtiff.lib
-

- -for the Release configuration.

- -The Ignore libraries field should contain: - -

-libcd.lib,libcid.lib,msvcrt.lib
-

- -for the Debug configuration and - -

-libc.lib,libci.lib,msvcrtd.lib
-

- -for the Release configuration.

- -The Additional library path field should contain - -

-c:\wx2\lib
-

- -for both Debug and Release configurations. - -

- -

Resources

- -Select your .rc file. The Additional resource include directories field should contain: - -

-c:\wx2\include
-

- -

Settings for wxWidgets 1.68

- -Note: these have not yet been checked.

- -

Debug: General

-The Executable for debug sessions field should be altered to be the path and name -you'd expect (it may have generated a different name).

- -

General

-The Output directories fields can be made blank if you want the objects -and executable to be created in the project directory and not a subdirectory.

- -

C/C++: Preprocessor

-The Preprocessor definitions field should contain the following symbols:

-WIN32,_DEBUG,_WINDOWS,wx_msw,DEBUG=1,WINVER=0x0400,STRICT
-

-The Additional include directories field should contain the following:

-../../include/base,../../include/msw
-

(and of course any other directories you wish to use in your project).

- -

C/C++: Precompiled Headers

- -The Not using precompiled headers or Automatic use of precompiled headers -button should be selected (I can't find a way of using the wxWidgets PCH file).

- -

C/C++: Code Generation

- -The Use run-time library control should be set to Multithreaded DLL. This -sets the compiler switch to /MD to match the wxWidgets makefile.

- -

Link: Input

- -The Object/library modules field should contain: - -

-kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib
-shell32.lib odbc32.lib odbccp32.lib comctl32.lib
-../../lib/wx.lib ../../src/msw/dummy.obj
-

- -The Ignore libraries field should contain: - -

-libcd.lib,libcid.lib
-

- -

Resources

- -Select your .rc file. The Additional resource include directories field should contain: - -

-..\..\include\msw
-

- -

- - - -