Class RunLoopModeTracker is implemented in both my.app/Contents/Frameworks/QtCore.framework/Versions/5/QtCore and /usr/local/Cellar/qt5/5.6.1/lib/QtCore.framework/Versions/5/QtCore. One of the two will be used. Which one is undefined.

When freezing applications with py2app, one could face problems as the one described in the Summary of this report:

```
Jun 14 10:00:06 my[6543] <Notice>: objc[6543]: Class RunLoopModeTracker is implemented in both my.app/Contents/Frameworks/QtCore.framework/Versions/5/QtCore and /usr/local/Cellar/qt5/5.6.1/lib/QtCore.framework/Versions/5/QtCore. One of the two will be used. Which one is undefined.
Jun 14 10:00:06 my[6543] <Notice>: objc[6543]: Class NotificationReceiver is implemented in both my.app/Contents/Frameworks/QtWidgets.framework/Versions/5/QtWidgets and /usr/local/Cellar/qt5/5.6.1/lib/QtWidgets.framework/Versions/5/QtWidgets. One of the two will be used. Which one is undefined.
```

Usually, one copies qt5 plugins in the Contents/PlugIns:

```
cp -R /usr/local/Cellar/qt5/5.6.1/plugins my.app/Contents/PlugIns
```

runs

```
/usr/local/Cellar/qt5/5.6.1/bin/macdeployqt dist/my.app -dmg
```

and the problem is solved. However, since qt5 (5.6.1) this is not true anymore. Is this a problem introduced by the new release?. As some of you may infer, I installed qt5 from homebrew. I reported there the problem, and they replied that no new changes where done in the packaging compared to version 5.6.0.

Please, feel free to close this report if it does not belong to the correct project.

Thanks.