> For the linking process, how could I have qcc do the linking instead of
> invoking icc, such as the example that I send it to you:
> 
> qcc -o foo foo.o -L<some libarary> -l<libray file>

Well you execute this, you're invoking the qcc conf files for gcc, so have a look at how the linker is invoked by qcc in
 the gcc conf files. $QNX_HOST/etc/qcc/gcc/3.3.5/gcc_ntox86.conf

You'll want to look at the parts for ld, ld_opt, ld_stdlib_path, ld_* parts in the conf files.You'll have to change ld 
to ntox86-ld, and then the ld_* opts to point to our lib dirs and then add in the icc libs.

From your output, its looks as if the compiler is actually a native Linux compiler, and you just want to link native 
Linux objects against QNX startup and libs -- which could work. But doesn't ICC for Linux have builtin include search 
paths, builtin defines, etc, that are specific to Linux? Is the mcpcom step before ld not necessary?  I'm curious why 
it's been implemented this way instead of how ICC 8.1 was done.

Regards,

Ryan Mansfield

Thanks!

Larry


-----Original Message-----
From: Ryan Mansfield [mailto:rmansfield@qnx.com] 
Sent: Friday, February 29, 2008 5:57 PM
To: momentics-community
Subject: Re: RE: RE: RE: RE: RE: RE: RE: add new compiler under QNX
Momentics IDE

> For the linking process, how could I have qcc do the linking instead
of
> invoking icc, such as the example that I send it to you:
> 
> qcc -o foo foo.o -L<some libarary> -l<libray file>

Well you execute this, you're invoking the qcc conf files for gcc, so
have a look at how the linker is invoked by qcc in the gcc conf files.
$QNX_HOST/etc/qcc/gcc/3.3.5/gcc_ntox86.conf

You'll want to look at the parts for ld, ld_opt, ld_stdlib_path, ld_*
parts in the conf files.You'll have to change ld to ntox86-ld, and then
the ld_* opts to point to our lib dirs and then add in the icc libs.

From your output, its looks as if the compiler is actually a native
Linux compiler, and you just want to link native Linux objects against
QNX startup and libs -- which could work. But doesn't ICC for Linux have
builtin include search paths, builtin defines, etc, that are specific to
Linux? Is the mcpcom step before ld not necessary?  I'm curious why it's
been implemented this way instead of how ICC 8.1 was done.

Regards,

Ryan Mansfield


_______________________________________________
QNX Momentics Community Support
http://community.qnx.com/sf/go/post5439

Hello Ryan,
	Since the subject is related to collaboration between QNX and
Intel, I prefer to discuss with you through company e-mail instead of
posting to the forums over QNX website. Please let me if this is an
issue.
	My new problem with QNX IDE is that I'm working on integrating a
couple of Window libraries (I assumed it's PE format) into QNX through
Momentics IDE. I got the following error messages while qcc intends to
link (I choose the GCC 3.2 as the compiler).

-oC:/QNX632/ide4-workspace/smoke_test/x86/o/smoke_test    smoke_test.o
-L. -LC:/opt/Intel/IPP/5.3.1.064/ia32/lib
-LC:/QNX632/target/qnx6/x86/lib/gcc/3.3.5
-LC:/QNX632/target/qnx6/x86/lib -LC:/QNX632/target/qnx6/x86/usr/lib
-Bstatic    -lC:/opt/Intel/IPP/5.3.1.064/ia32/lib/ippsemerged.lib
-lc:/opt/Intel/IPP/5.3.1.064/ia32/lib/ippsmerged.lib    -Bdynamic     
/cygdrive/c/QNX632/host/win32/x86/usr/bin/i386-pc-nto-qnx6.3.0-ld:
cannot find -lC:/opt/Intel/IPP/5.3.1.064/ia32/lib/ippsemerged.lib
cc: C:/QNX632/host/win32/x86/usr/bin/i386-pc-nto-qnx6.3.0-ld caught
signal 1
make[2]: *** [C:/QNX632/ide4-workspace/smoke_test/x86/o/smoke_test]
Error 1
make[2]: Target `all' not remade because of errors.
make[2]: Leaving directory `C:/QNX632/ide4-workspace/smoke_test/x86/o'
make -j 1 -Co-g -fMakefile all
make[1]: [all] Error 2 (ignored)

	It looks to me that the IDE still uses the Linux library
convention (lib<library-name>). Does that mean I need to port my Linux
version of library here, instead of Windows? The other issue that I
found that over IDE GUI, I am supposed to be able to specify additional
library/include path, but the IDE won't accept any path string that has
<SPACE> in. Even that I tried to use an environment variable, once the
IDE expands the environment variables it creates two path strings when
it sees a <SPACE>.

Larry

-----Original Message-----
From: Ryan Mansfield [mailto:rmansfield@qnx.com] 
Sent: Friday, February 29, 2008 5:57 PM
To: momentics-community
Subject: Re: RE: RE: RE: RE: RE: RE: RE: add new compiler under QNX
Momentics IDE

> For the linking process, how could I have qcc do the linking instead
of
> invoking icc, such as the example that I send it to you:
> 
> qcc -o foo foo.o -L<some libarary> -l<libray file>

Well you execute this, you're invoking the qcc conf files for gcc, so
have a look at how the linker is invoked by qcc in the gcc conf files.
$QNX_HOST/etc/qcc/gcc/3.3.5/gcc_ntox86.conf

You'll want to look at the parts for ld, ld_opt, ld_stdlib_path, ld_*
parts in the conf files.You'll have to change ld to ntox86-ld, and then
the ld_* opts to point to our lib dirs and then add in the icc libs.

From your output, its looks as if the compiler is actually a native
Linux compiler, and you just want to link native Linux objects against
QNX startup and libs -- which could work. But doesn't ICC for Linux have
builtin include search paths, builtin defines, etc, that are specific to
Linux? Is the mcpcom step before ld not necessary?  I'm curious why it's
been implemented this way instead of how ICC 8.1 was done.

Regards,

Ryan Mansfield


_______________________________________________
QNX Momentics Community Support
http://community.qnx.com/sf/go/post5439

> Hello Ryan,
> 	Since the subject is related to collaboration between QNX and
> Intel, I prefer to discuss with you through company e-mail instead of
> posting to the forums over QNX website. Please let me if this is an
> issue.
> 	My new problem with QNX IDE is that I'm working on integrating a
> couple of Window libraries (I assumed it's PE format) into QNX through
> Momentics IDE. I got the following error messages while qcc intends to
> link (I choose the GCC 3.2 as the compiler).

Hello Larry,

If you need to discuss anything sensitive that cannot be discussed on the forums, you can email me privately at 
rmansfield@qnx.com. If there's general questions about qcc or IDE integration that can be publicly discussed, we'd 
really like to do it on the Foundry so the information is available for others to learn.

You won't be able to link and execute PE libraries into QNX. We only support ELF binaries on Neutrino. If you're trying 
to link in any libraries to run on QNX, they should be built with a cross compiler (gcc or icc) that specifically 
targets QNX. 

I believe the spaces in the include paths are a known issue. I'll do some investigation and get back to you.

Regards,

Ryan Mansfield