- I redid the “configure” and enabled many more options. I also tried many more –host choices and settled on i686-mingw32

- In NetBeans, the `wx-config –libs` can only go into one place:

In Project, choose properties. Then, go to the linker section. Find the “Libraries” line and expand the “…” button. Click “Add Option” then choose the “Other Option” button. Enter `wx-config –libs` here.

After several days, ‘hello world’ compiles and links. These are all good systems but there so many options and platforms, that a detailed description needs to be written for each different setup. The general purpose setups suffer because of the lack of documentation. I thank you again for this best tutorial and am happy to contribute my own writing if wanted.

Comments:

First, I am building the Hello World example, nothing custom or special.

- “configure” fails unless I set –host i386-mingw (miracle I figured this out — this option I could not find documented anywhere, even in ‘configure –help’).

- Easier than typing the wx-configure line, I added this to the compiler options:

`{full-path}/wx-config –cxxflags`

Note that these are backticks and NOT single quotes. This executes the command on the fly and is less error prone I feel. Similar option for linker is possible.

- step 13 is the breaking point. I did everything you said in every possible combination but I still get the ugly linker errors. I must need different options during configure, but what? Too many choices.

My setup: Windows 7 on intel i3, NetBeans 6.9, wxWidgets 2.8.11, MinGW 5.1.6, MSys 1.0.11 (I don’t think this is the latest version, but the newer versions don’t seem to include ‘make’ and NetBeans won’t work with MinGW’s make).

To use accents directly in your code you have to make sure that:

1. Your wxWidgets build supports unicode. Check the 5th step of the first part of the tutorial for more info;
2. You are using the _T or wxT macros. It is a good practice to always use one of these macros whenever you use literal strings because even if you use an ASCII only build, these macros will simply return the value you’ve passed;
3. You are using unicode codes for every non ASCII character. For example: instead of using "Ação", you must use _T("A\u00E7\u00E3o").

So uma pergunta como habilitou o wxWidgets para mostrar acentos?

This is usually a lib configuration problem. Try removing all the lib configuration and compile it again. If you get the same error, the libraries weren’t configured correctly.

any idea?

One problem is that numerous programming language books *do* have example problems. Another is that if you did publish the example database, then invariably, their solutions would start appearing.

My best idea so far is a heavily-moderated wiki, with no solutions allowed, or a proprietary database sold only to employers. If solutions appear online (or someone writes a book and starts selling it), then all testing happens in the interview (no take-homes).

Now someone needs to register a domain, set up the wiki and categorizing/rating systems, and start transcribing problems from texts. Simple, right?