Clean was the first thing I tried too, didn't help. I am building from the command line, but on Windows; perhaps it has something to do with path parsing in the map file?
On 27 Feb. 2017 9:03 am, "Szymon Janc" <[email protected]> wrote: > Hi, > > On 27 February 2017 at 17:19, Sterling Hughes > <[email protected]> wrote: > > I had the same problem and solution. Also, make sure you are using the > > “right” (arm-elf-eabi-none-nm) nm. The native nm on Mac OS X doesn’t > > provide the right information. > > > > Sterling > > > > > > On 27 Feb 2017, at 2:36, Szymon Janc wrote: > > > >> Hi Simon, > >> > >> On 26 February 2017 at 23:53, Simon Ratner <[email protected]> wrote: > >>> > >>> Looks neat, but when I run it, I don't get the tree -- everything is > >>> lumped > >>> under "(other)". Any ideas? > >> > >> > >> I initially had the same issue but this was gone when I did 'newt clean' > >> and rebuild everything from scratch. Not sure why this was needed. > > So did few more tests and it looks like building from Eclipse (as > described on > Codecoup blog) seems to result in flat structure for 'newt size -F'. > > While building from shell it seems to work just fine. Will need to > figure it out why:) > > -- > pozdrawiam > Szymon K. Janc >
