This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See crosstool-NG for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Is C++ supported ????


Thanks.
Well explained (for a newbie....)

I have other questions but I'll open a new thread for them....


On Mon, Dec 30, 2013 at 10:04 PM, Niels Penneman <niels@penneman.org> wrote:
> You can see it from the config file:
>
> CT_PREFIX_DIR="${HOME}/x-tools/${CT_TARGET}"
> CT_INSTALL_DIR="${CT_PREFIX_DIR}"
>
>
> This is a default setting. If you make a new configuration and don't
> change this, crosstool-ng will make an x-tools directory in your home
> folder ${HOME}, and inside x-tools it will make a subdirectory with the
> name of your target, ${CT_TARGET}, in this case "i686-zm-linux-gnu".
>
> How to change this / see it in the configuration menu:
> First, bring up the menu using nconfig or menuconfig:
>
> # ct-ng nconfig
>
> Then, go into the "Paths and misc options" menu, find "Prefix directory"
> and change it. That should do the trick.
>
>
> On 12/30/2013 08:20 PM, Mau Z wrote:
>> Thanks again
>> Actually now buildroot finished it's job.
>>
>> So I really wonder one more thing (This is just curiosity, since thing
>> look like working) :
>>
>> Where did I tell crosstool-ng to create the "x-tools" directory in my
>> home directory ?
>>
>> Really thanks
>>
>>
>> On Mon, Dec 30, 2013 at 8:30 PM, Niels Penneman <niels@penneman.org> wrote:
>>> Hi,
>>>
>>> Notice that the compiler you are referring to below is called
>>> i686-build_pc-linux-gnu-g++, not i686-zm-linux-gnu-g++. The build_pc
>>> part indicates that the compiler mentioned below is the compiler used to
>>> build the cross-compiler, not the cross-compiler itself. This is why it
>>> is just a shell script that invokes your host compiler in /usr/bin.
>>>
>>> On 12/30/2013 06:34 PM, Mau Z wrote:
>>>> Hi again,
>>>>
>>>> Thanks for the quick advice.
>>>>
>>>> Do you mean that I should put :
>>>> BR2_TOOLCHAIN_EXTERNAL_PATH="/home/zm02/development/crosstoo-ng/crosstool-ng-1.18.0/toolChain/.build/i686-zm-linux-gnu/build/build-cc-final/gcc/
>>>>
>>>> I tried it, but it did not work.
>>>>
>>>> Does crosstool-ng produce g++ for the target ???
>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>> I am asking because the following file "i686-build_pc-linux-gnu-g++"
>>>> is actually a script which activated  /usr/bin/g++
>>>> Here is the content of this file :
>>>> #!/bin/bash
>>>> exec '/usr/bin/g++' "${@}"
>>>>
>>>> The file "i686-build_pc-linux-gnu-gcc"  (which is located in the same
>>>> directory), is similar :
>>>> #!/bin/bash
>>>> exec '/usr/bin/gcc' "${@}"
>>>>
>>>>
>>>> Now if you compare it to  "i686-zm-linux-gnu-gcc" (which is located in
>>>> the same directory), then this is a "real program"
>>>> ls -l i686-zm-linux-gnu-gcc
>>>> -rwxr-xr-x 2 User_01 User_01 1454560 Dec 30 08:50 i686-zm-linux-gnu-gcc
>>>> But there is no file named  "i686-zm-linux-gnu-g++"
>>>>
>>>>
>>>>
>>>>
>>>> Thanks again
>>>> Mau
>

--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]