cancel
Showing results for 
Search instead for 
Did you mean: 

Can SW4STM32 be configured to use GCC v4.9 ?

Andrew Neil
Evangelist III
Posted on May 30, 2017 at 13:45

Cross-post: 

http://www.openstm32.org/tiki-view_forum_thread.php?forumId=7&threadId=5150&comzone=show&sharpthreadId5150

  

SW4STM32 seems to come with GCC v5

Working with exported mbed projects requires GCC v4.9.

Can the SW4STM32 be configured to use GCC v4.9 ?

If so, how?

Thanks.

#eclipse #sw4stm32-eclipse #sw4stm32 #gcc #mbed
8 REPLIES 8
Andrew Neil
Evangelist III
Posted on May 30, 2017 at 15:09

I see this has been marked as an 'Action Item' - what does that actually mean?

Posted on May 30, 2017 at 16:05

Hi

Neil.Andrew

,

I see this has been marked as an 'Action Item' - what does that actually mean?

This means that your entry is under review.

-Nesrine-

Andrew Neil
Evangelist III
Posted on May 31, 2017 at 09:15

Cross-post: 

http://www.openstm32.org/tiki-view_forum_thread.php?forumId=7&comments_parentId=5150

 - a 'hack' is noted as a workaround.

But this is really a Big Issue for anyone wanting to export anything for STM32 from mbed.

Julien D
ST Employee
Posted on May 31, 2017 at 10:07

Hi Andrew,

2 solutions were described on OpenSTM32 forum to not stay blocked with this issue

A clean way to configure the toolchain in use within the project properties and indeed another considered as a 'hack'.

The first do the job and should be acceptable while you don't have plenty of projects to configure.

Posted on May 31, 2017 at 09:02

Thanks,

ELMHIRI.Syrine

- but still unclear what that actually means.

Is that for forum moderation? Or the SW4STM32 development team? Or ...

Posted on June 07, 2017 at 18:46

I tried tried setting the path in the Project Properties, and it didn't work - see the other thread.

Posted on June 09, 2017 at 11:28

Looking your System Workbench version (1.13.1) and our bugs database I confirm that the defect your are facing is fixed since 1.14.

It's time to give a chance to version 2.0 !

Posted on June 09, 2017 at 14:44

going to give v2.0 a go ...