CPU Overload

[easiwriter]

The fan on my laptop is running continuously when I work on my app. I am slowly modularising it to reduce the length of compilations. I am using a 2.6 GHz Intel machine with 32Gb of memory. Do others ha the same problem?

[easiwriter]

Further to the post above I have regretfully had to abandon my attempt to modularise my app because of endless inexplicable compilation errors involving 'failed to find module' on import statements, despite the fact that the module was there. I've felt like I'm chasing my tail all the time and it was driving me nuts. I have no idea why this has been happening. I've tried clean builds in Xcode and swift builds from the terminal. One import works for no reason then another fails. I suspect as mentioned above that the problem is my laptop not having enough oomph and this is causing Swift to break. Any other suggestions welcome.

[stephencelis]

Sadly I think the bugs you are encountering are pretty general issues and not related specifically to TCA. A repro might help us give you more hints on what to check in Xcode, etc., but I'd suggest checking the activity logs to see if any errors are there that aren't getting surfaced directly in Xcode's UI, perhaps in an SPM-related log, or in a build log. You could also try resetting your packages, delete your derived data folder, etc. I've had to reboot my entire computer to address intermittent Xcode issues in the past...

[easiwriter]

Thanks Stephen

I will research this some more tomorrow (I am at least 5 hours ahead of you). If I don't make any headway would you be prepared to look at the project if I send a copy? The unmodularised project compiles OK, as do the examples you supply, so something weird is going on. If it compiles for you then the problem must be with my system.

Best
Keith

[stephencelis]

I can give it a shot!

[easiwriter]

I've discovered that if I get Xcode to build the package it works ok, but if I ask it to compile the app afterwards (no clean) it throws compilation errors. Not only that but it seems to compile as if it was a clean build when the only code is the single app source which imports the library.

The project is too big to upload so I've added you as a collaborator to the GitHub repo (I think).

[frolo1]

This sounds like an access issue. Maybe it helps making your feature public?

https://docs.swift.org/swift-book/documentation/the-swift-programming-language/accesscontrol/#Access-Levels-for-Frameworks

When you develop a framework, mark the public-facing interface to that framework as open or public so that it can be viewed and accessed by other modules, such as an app that imports the framework. This public-facing interface is the application programming interface (or API) for the framework.