• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 81 subscribers
  • Views 851 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430FR5994: How is one suposed to deal with the MACOS dot files that are unrelated to CC and causing compile/debug errors?

DaveC
Prodigy 240 points
Part Number: MSP430FR5994


I have to believe this has been asked before but believe it or not, I cannot find a question for this issue.

I am running CC on mac os Venture 13.1. When I compile, I get errors for (primarily) the following:

"Description Resource Path Location Type
Content is not allowed in prolog. in file /Volumes/T7-MBx86/projects/MSP4305994/poop/targetConfigs/._MSP430FR5994.ccxml ._MSP430FR5994.ccxml /poop/targetConfigs line 1 Problem"

So, it astounds me that CC is even paying attention fo the classic max os "._xxx" files. I am further astounded that there is no setting to view and ignore these files within CC. I would have expected to see something in the README.txt file when I installed CC on the mac. I initially tried using Parallels with Windows 10, but I am using an older launch pad (MSPfr5994) which, I know, has issues with the USB, or so I thought.

Anyway, not to sound cynical, just wondering what others do with the unrelated (to CC) "dot files"?


Thanks,

Dave Comer

  • 0
    Guru 100415 points

    I don't know how the MacOS "._" naming convention works exactly, but *.ccxml files are created/managed by CCS (in my Windows system they're in the targetConfigs directory).

    Did you create these files? Maybe try a different suffix.

  • 0 in reply to Bruce McKenney
    Prodigy 240 points

    Hi Bruce, and thanks for the reply. I use CC on my Dell laptop or have in the past, and it works well. As of the past two years, I find using a MAC running parallels (a popular VM on macs) with several choices of environments such as ubuntu, Windows 10, Windows 11, BSD, and even mac clones.) I know that's beside the point, but it allows one to use one powerful machine to develop.) 

    So, one annoyance is that mac creates what I guess you can describe as "configuration files" to help programs. In the case of CC I think it may be down to one that affects CC, and that is the file ._*.ccxml aside along with if the CC produced *.ccxml file (I'm shortening the name for convenience.) In effect, it means that every time you compile you have to delete the mac produced "configuration file" as, I think, the debugger gets confused. It may not seem like much, and I will probably put a rule in the make file to delete this mac artifact, but I raised the issue as the developers of CC should have been aware of the nuances of the mac os. It's not specific to a release, it's the way mac works. 

    So, thanks for your reply and time. I'm hoping the developers of CC can shed some light on why CC doesn't ignore these config files.

    Dave

  • +1 in reply to DaveC
    Prodigy 240 points

    Nothing like replying to yourself, right? I found a solution, although I'm open to better ideas. In the reply to a similar question;

    https://apple.stackexchange.com/questions/14980/why-are-dot-underscore-files-created-and-how-can-i-avoid-them

    wiliam listed writes:

    "From man dot_clean: For each dir, dot_clean recursively merges all ._* files with their corresponding native files according to the rules specified with the given arguments. By default, if there is an attribute on the native file that is also present in the ._ file, the most recent attribute will be used. This command does not just remove certain dot files, it may overwrite previous/native attributes for each folder. Use with caution."

    Apparently, if you have an HFS+ formatted partition, you do not get dot files generated automatically However, HFS+ is used on Apple systems, and may not be accessible to other operating systems (e.g. Parallels Linux or Windows OS).

    The above is a very informative link for others that may experience what I am. I rand the dot_clean (will am considering adding it to make). And I can now develop for the MPS430 on macOS.

    I thoughtsomeone else may want or need this information.

    Dave

  • 0 in reply to DaveC
    TI__Mastermind 23105 points

    Hi Dave

    Thanks for your sharing!

  • 0 in reply to Xiaodong LI
    Prodigy 240 points

    Sure. One additional note; I learned that if you can also select the filters and customizations icon above the project explorer, then select the pre-set filters tab, and finally uncheck the .* resources item and you will see all hidden (dot) files. You can delete the offending macOS-created files there as well. It would be nice if CC had a mac aware update to automatically remove any dot files that conflicted with the legitimate files used in the project though. That said, the mac version works just fine for me now.

  • 0 in reply to DaveC
    Guru 42145 points

    I think this is only an issue if you use the finder to work with the files. TI's tools don't add the resource files. (Historical note: each file in the Mac OS file system used to have two "forks", a data fork and resource fork. The data fork would contain what we think of as the file, while the resource fork would contain icon info and stuff like that. To get better compatibility with other OS's, they dropped that approach. Since there was still a need for the resource info, the resource file ("dot file") was born.)

  • 0 in reply to Keith Barkley
    Prodigy 240 points

    Keith, thanks for the detailed reply. I agree based on what I am reading, although, I have noticed that when I create a project using the new project->CC managed, there are some of the dot files that do show up. I don't see getting away from using finder as a solution; at least not in my case. However, I also read that if I had an HPS+ partitioned filesystem (perhaps on an external disk, the information that is contained in the dotfiles (._*) is no longer created and is placed in created files as metadata. However, if all I have to do is delete the dotfiles on occasion, I can live with that, Or, maybe modify my make file to add a dot_clean or rm -rf ._* that may be a decent workaround. I'd rather focus on the embedded code and not the OS, but, that is the life of an embedded developer I suppose.

**Attention** This is a public forum