Author Topic: CB 8.02 backticks problem  (Read 4985 times)

Offline spectrum

  • Multiple posting newcomer
  • *
  • Posts: 16
CB 8.02 backticks problem
« on: June 22, 2009, 03:58:44 pm »
Hi all,

on project->settings, linker->settings:

`wx-config --libs` expand fine

`wx-config --libs --unicode=no` expand to nothing (empty)

but on the osx shell,
wx-config --libs --unicode=no

magically expand right to:
-L/usr/local/lib   -framework IOKit -framework Carbon -framework Cocoa -framework System -framework QuickTime -framework OpenGL -framework AGL  -lwx_mac_richtext-2.8 -lwx_mac_aui-2.8 -lwx_mac_xrc-2.8 -lwx_mac_qa-2.8 -lwx_mac_html-2.8 -lwx_mac_adv-2.8 -lwx_mac_core-2.8 -lwx_base_carbon_xml-2.8 -lwx_base_carbon_net-2.8 -lwx_base_carbon-2.8

So, i read many posts that bacticks/CB works perfetc, but don't seems.

Greetings,
Angelo









Offline stahta01

  • Lives here!
  • ****
  • Posts: 7591
    • My Best Post
Re: CB 8.02 backticks problem
« Reply #1 on: June 22, 2009, 04:32:48 pm »
Which version of 8.02 are you using?
It was patched once or twice for Mac OS.
Note, I am a windows user so not sure how to tell which patch version you are using.
Tim S
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline spectrum

  • Multiple posting newcomer
  • *
  • Posts: 16
Re: CB 8.02 backticks problem
« Reply #2 on: June 22, 2009, 04:55:38 pm »
it is build 28 feb 2008 just downloaded.

greetings

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7591
    • My Best Post
Re: CB 8.02 backticks problem
« Reply #3 on: June 22, 2009, 06:19:33 pm »
I would suggest trying the 21 Mar 2008  patched 2 version; no idea what it fixes.

http://www.codeblocks.org/downloads/5

Tim S
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884
Re: CB 8.02 backticks problem
« Reply #4 on: June 23, 2009, 11:16:40 am »
I would suggest trying the 21 Mar 2008  patched 2 version; no idea what it fixes.

Code::Blocks is exactly the same in all three, just that the bundled wxWidgets
was "patched" to fix a multi-threading issue that would cause it to hang...

There's some nightly builds as well, if anything changes when using those ?
http://developer.berlios.de/project/showfiles.php?group_id=5358

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884
Re: CB 8.02 backticks problem
« Reply #5 on: June 23, 2009, 11:20:44 am »
on project->settings, linker->settings:

`wx-config --libs` expand fine

`wx-config --libs --unicode=no` expand to nothing (empty)

but on the osx shell,
wx-config --libs --unicode=no

magically expand right to:
-L/usr/local/lib   -framework IOKit -framework Carbon -framework Cocoa -framework System -framework QuickTime -framework OpenGL -framework AGL  -lwx_mac_richtext-2.8 -lwx_mac_aui-2.8 -lwx_mac_xrc-2.8 -lwx_mac_qa-2.8 -lwx_mac_html-2.8 -lwx_mac_adv-2.8 -lwx_mac_core-2.8 -lwx_base_carbon_xml-2.8 -lwx_base_carbon_net-2.8 -lwx_base_carbon-2.8

So, i read many posts that bacticks/CB works perfetc, but don't seems.

Try with `/usr/local/bin/wx-config` (full path) instead of `wx-config`,
so that you aren't picking up the ancient /usr/bin/wx-config by mistake...

It would give an error (instead of output) when trying in the ANSI mode:
Code

  Warning: No config found to match: /usr/bin/wx-config --libs --unicode=no
           in /usr/lib/wx/config
  If you require this configuration, please install the desired
  library build.  If this is part of an automated configuration
  test and no other errors occur, you may safely ignore it.
  You may use wx-config --list to see all configs available in
  the default prefix.


Offline foobar123

  • Multiple posting newcomer
  • *
  • Posts: 17
Re: CB 8.02 backticks problem
« Reply #6 on: March 04, 2010, 12:13:36 am »
On Linux, with C::B svn rev. 5986, the backtick command
 `date +"%F %H:%M"`
also generates an empty string, while `date +%F` works as expected.