summaryrefslogtreecommitdiff
path: root/src/plugins/ios/iosrunfactories.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Pass id to RunConfiguration constructorhjk2018-04-251-45/+0
| | | | | | | | | | | It's what the base class requires, and opens the possibility to have several factories creating the same type of run configuration. Also move ios, winrt and android factories closer to their products, it's the predominant pattern nowadays. Change-Id: Iad48152f02a248d22cb18dd435a2fc34d73c7077 Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* iOS: Use base method to list run configurationshjk2018-03-271-18/+0
| | | | | | | The base method is good enough nowadays. Change-Id: I1affc678a2168d002ed8f627a56f172e30c1c0be Reviewed-by: Vikas Pachdha <vikas.pachdha@qt.io>
* ProjectExplorer: Let RunConfiguration declare what nodes it belongs tohjk2018-03-161-6/+0
| | | | | | | | | | | | | | | | | | | This feature in question is the availability of the "Run" button in the context menu of certain project nodes in the project tree to run something presumably related to/build from that (sub)project. Previously, the decision was made for certain qmake based projects (those targeting Desktop, iOS and VxWorks) by some indirection through the corresponding RunConfigurationFactories. The patch lets the RunConfigurations decide themselves directly and removes the indirection, potentially opening the feature for other qmake based RCs, as well as other combinations (e.g. PythonRunConfiguration could be associated with its .py file, without the need to have a dummy project) Change-Id: Ic489bd1dfa25fcd9102ffa4fa30125565dd2e40e Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* Merge remote-tracking branch 'origin/4.6'Eike Ziller2018-03-131-1/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: src/plugins/cmakeprojectmanager/cmakeproject.h src/plugins/debugger/debuggerplugin.cpp src/plugins/ios/iosrunfactories.cpp src/plugins/nim/project/nimproject.h src/plugins/qbsprojectmanager/qbsrunconfiguration.cpp src/plugins/qmakeandroidsupport/qmakeandroidrunfactories.cpp src/plugins/qmakeprojectmanager/desktopqmakerunconfiguration.cpp src/plugins/qmlprojectmanager/qmlproject.h src/plugins/qnx/qnxrunconfigurationfactory.cpp src/plugins/qtsupport/exampleslistmodel.cpp src/plugins/winrt/winrtrunfactories.cpp Change-Id: Ib029fdbaa65270426332f5edd6e90264be5fb539
| * RunConfigurationFactories: Fix crash opening non-qmake based projectsTobias Hunger2018-03-071-1/+2
| | | | | | | | | | | | | | | | | | Make sure the Qnx RCs only get triggered for qmake-based projects and defend against broken set-ups using QTC_ASSERT. Task-number: QTCREATORBUG-19755 Change-Id: If64b73de49b0199308f767151d68909dc8b1bc53 Reviewed-by: hjk <hjk@qt.io>
* | Rename IRunConfigurationFactory to RunConfigurationFactoryhjk2018-03-071-3/+1
| | | | | | | | | | | | | | | | | | | | | | It's not an *I*nterface anymore Also, remove the in-all-but-one case unused QObject parent and the object name that was only there for debugging purposes. The class type serves the same purpose in the debugger. Change-Id: I0dafb01e6b4fd7c7df04a63aaa3ef3e4bd693f6f Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* | Introduce and use IRunConfiguration::addSupportedTargetDeviceTypehjk2018-02-231-1/+2
| | | | | | | | | | | | | | | | | | | | | | In line with addSupportedProjectType, saves a few cycles due to the non-use of the temporary list, and in theory more flexible than the existing set...(QList<Id>) as it potentially allows dependent plugin to declare support for already existing configurations instead of re-implementing their own. Change-Id: I2b83e90de49daa9bfce6f780c5f51c2e971eb7d1 Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* | ProjectExplorer: Simplify collection of RunConfigurationCreationInfoshjk2018-02-151-14/+3
| | | | | | | | | | | | | | | | | | Instead of calling twice for AutoCreated and UserCreated, call once and record to which case it belongs. Only the 'both' and 'user only' combination are ever used. Change-Id: I9c15085bcbb4bf6584a6156135f2084dbfc51c1c Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* | IRunConfiguration: Remove BuildTargetInfo from the RC factory APIsTobias Hunger2018-02-061-9/+12
| | | | | | | | | | | | Change-Id: I1d77d22a1c1ce1cbcfca8af7855ae7b935ac1c2c Reviewed-by: Christian Kandeler <christian.kandeler@qt.io> Reviewed-by: hjk <hjk@qt.io>
* | Ios: Do not report AuxTemplates as availableBuildTargethjk2018-01-181-2/+1
|/ | | | | | | | This is different from all other target platforms, and was part of the initial ios code without anyone being around who knows why. Change-Id: I8be4094b89deb32275fc08b3c1560d7d5610ea28 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
* QmakeProject: Centralize some code for subproject runconfig handlinghjk2018-01-111-9/+3
| | | | | Change-Id: Iecd8c326fc7fd1b1e7e5406fd899befc9fdd3c5b Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* QmakeProject: Make availableBuildTargets return a BuildTargetInfo listhjk2018-01-111-16/+7
| | | | | | | It's what the "consumer side" expects. Change-Id: I1a4e75eda09f8626fcf65290e6c58a08eed9fdca Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* ProjectExplorer: Return BuildTargetInfo from availableBuildTarget()hjk2018-01-051-9/+17
| | | | | | | | | | | | | ... including build target name and display names instead of returning QString build target names and producing display names via displayNameForBuildTarget() This is a mechanical intermediate step on the road to use Target::applicationTargets().list uniformly as source of build targets. Change-Id: I7b0b1fb398d5061b0cec0b86890f9eaf0bb53a19 Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* ProjectExplorer: Use ids in RunConfigFactory:: setSupportedProjectTypehjk2017-12-191-2/+2
| | | | | | | More similar to what build/deploy uses. Change-Id: Icf8bd7031d00a6e2831f8c1f3b1bdcaa8bf259b4 Reviewed-by: hjk <hjk@qt.io>
* Ios: Use device types as restrictions on project configurationshjk2017-12-191-6/+1
| | | | | Change-Id: I3c31f14eba9d9f68a333a814bea800a3da38d4a2 Reviewed-by: Vikas Pachdha <vikas.pachdha@qt.io>
* ProjectExplorer: Register createes' base id in RunConfigurationFactoryhjk2017-11-271-27/+9
| | | | | | | | | | | | | | | This shifts the resposibility of creation/splitting of RunConfiguration ids into what are essentially "type ids" and "build targets" to the base implementation, possibly opening the path of abandoning the mangled ids in favor of explicitly storing their constituent parts. Take advantage of base id split in RunConfigurations for availableIds /displayNameForId and for canCreate/canRestore/canClone. Change-Id: I19fefb32757407ab5053a2ae0e5a79438659f6ec Reviewed-by: Christian Kandeler <christian.kandeler@qt.io> Reviewed-by: Tobias Hunger <tobias.hunger@qt.io> Reviewed-by: Filippo Cucchetto <filippocucchetto@gmail.com>
* ProjectExplorer: Add a RunConfigurationFactory::canHandle(Target *)hjk2017-11-201-9/+2
| | | | | | | | All RunConfiguration factories had some kind of canHandle(Target *) implementation. Centralize this notion. Change-Id: Ie24a355e857bddfd76b866859b8c7a42ffc83840 Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* ProjectExplorer: Implement RunConfiguration::do{Clone,Restore} in basehjk2017-11-161-11/+0
| | | | | | | | It's possible now. Change-Id: I49ed73312aea1627a9543890431e2e379e3fb3ec Reviewed-by: Tobias Hunger <tobias.hunger@qt.io> Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* Ios: standardize IosRunConfiguration::initialize() signaturehjk2017-11-151-19/+7
| | | | | | | | Most other signatures look like RunConfiguration::initialize(Core::Id), this here is part of unifying them completely. Change-Id: I7cd2acc8ebe6ec8cef05272f18f0fa5ded94f930 Reviewed-by: Vikas Pachdha <vikas.pachdha@qt.io>
* ProjectExplorer: Simplify IRunConfigurationFactory::clone() usehjk2017-11-141-9/+2
| | | | | Change-Id: I005d6c87142d26dfc7ae1349329737a68f54c427 Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* ProjectExplorer: Re-organize RunConfiguration constructorshjk2017-09-131-4/+3
| | | | | | | | | | | | | | | | | | | | The idea is to massage the setup in a way to make implementation of new configurations less error prone by identifying recurring patterns and sharing repetitive code that tends to be forgotten (see Android cloning). The former two lines of constructors (owner-and-id, owner-and-source) are split into a simple, shared, constructor and new setId() and copyFrom() functions. The change is mostly mechanical, some multiple calls to fromMap have been removed, though, some consts added. Otherwise, to keep the patch small it temporarily introduces two helper templates in IRunConfigurationFactory. Also, setId() signatures have not been unified yet. These won't be needed in the final setup. Change-Id: I8c0734496caae744a9883fe6d92c1d8f8e0234ea Reviewed-by: hjk <hjk@qt.io>
* iOS: Dissolve IosRunControlFactoryhjk2017-07-171-49/+0
| | | | | | | Follows suite. Change-Id: I2ef11d19d9a2d3d0f3f282a94f98a40478273fbc Reviewed-by: Vikas Pachdha <vikas.pachdha@qt.io>
* Debugger: Use a somewhat less intrusive hack for 'start at main'hjk2017-07-121-1/+0
| | | | | Change-Id: Ie649a4a11c88f3686cd6ed1e73f34c7c78fd0e13 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* Ios: Re-enable QmlProfilerhjk2017-06-271-2/+1
| | | | | | Change-Id: I55a102c8f3a0c748b483a2fa36aa51947d13764a Reviewed-by: hjk <hjk@qt.io> Reviewed-by: Vikas Pachdha <vikas.pachdha@qt.io>
* Debugger, QmlProfiler et al: Replace AnalyzerStartParameterhjk2017-06-161-1/+0
| | | | | | | | | | | ... and QmlProfilerRunner::Configuaration by PE::UrlConnection, and call it 'serverUrl' on the user side. That's the only variant we ever had and avoids "translations" between three structures that are essential the same. Change-Id: I33386b2b8d2a7985ff934f6f8f840de0831bf9c1 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* Ios: Convert to RunWorkershjk2017-06-121-24/+13
| | | | | | | | | | This moves all of the RunControl implementation into a single RunWorker, not yet splitting it up into separate RunWorkers which is the final goal of this series. Done-with: Vikas Pachdha Change-Id: I9deaef48735c1c63c41dfae39d67f59387295273 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* ProjectExplorer: Split Target and ToolRunners into smaller taskshjk2017-05-151-5/+2
| | | | | | | | This increases re-usability of activities like 'port gathering', and makes their use less dependent on actual device implementations. Change-Id: I017cb74874f2b38c487ba2d03906a675d5618647 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* ProjectExplorer: Merge AnalyzerRunControl into RunControlhjk2017-04-051-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | The change is "conceptually wrong", the AnalyzerRunControl derived classes' functionality should be provided by ToolRunners based classes encapsulating/"being" the current Analyzer*Runner classes. However, the AnalyzerRunControl is only three (empty even) virtual functions, but a big obstacle in merging attempt due to a lot of mechanical followup changes in downstream users. The current construction mechanism of analyzer run controls is actually two different mechanisms (locally direct RunControlFactories, and a "generic" createAnalyzerRunControl wrapper for remote cases). The generic createAnalyzerRunControl makes it difficult to migrated them one-by-one, due to the various downstream users. So instead of merging the per-analyzer two uses directly reduce the "indirection" distance by removing the AnalyzerRunControl intermediate layer. After that the createAnalyzerRunControl mechanism can be dissolved by using normal RunControlFactories also for the remote cases. After that, porting to ToolRunner, and combining with ther local equivalent can be done one by one. Change-Id: I0ddace33fcce210cf3a547ac5bb23b3d85013934 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* iOS: Adapt to introduction of ProjectExplorer::ToolRunnerhjk2017-03-301-1/+1
| | | | | | Change-Id: I53201edb58485c697c8c56db68ddefd3cf107193 Reviewed-by: Vikas Pachdha <vikas.pachdha@qt.io> Reviewed-by: hjk <hjk@qt.io>
* ProjectExplorer: Run RunControl::{start,stop} always asynchronouslyhjk2017-03-241-1/+1
| | | | | | | | | | | | | | | | This introduces a mini-state-"machine" to handle RunControl states Intialized->[Starting->Running->Stopping->Stopped->]*->Finished. Needing time between trying to start and getting feedback is nowadays the normal setup for all remote targets as well as for most local tools. Making that the default for all runs simplifies the code and provides an opportunity to (a) fix some currently wrong reports of "stopped immediately" and (b) to remove target-specific (WinRT) or tool-specific (Valgrind, GammaRay) state members doing essentially the same. Change-Id: I7f52fee41144188ee8389e922fdc265f8c0a6459 Reviewed-by: David Schulz <david.schulz@qt.io> Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* QMake: Simplify QmakeProject::creationIds use furtherhjk2017-02-281-5/+4
| | | | | | | | We always operate on specific types of proFiles, knowing the types suffices as interface. Change-Id: I5ffe8862ae31234843a71bdae537825b37ccd311 Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* QMake: Centralize determination of available creationIdshjk2017-02-281-5/+2
| | | | | | | | No need for each target to do essentially the same. Change-Id: I76b6a0f2d064d7721f4ebe676f6efe12d3b5f87c Reviewed-by: BogDan Vatra <bogdan@kdab.com> Reviewed-by: Vikas Pachdha <vikas.pachdha@qt.io>
* Remove spaces in initializer listsTim Jenssen2017-02-221-3/+3
| | | | | | | Format initializer lists code style like. Change-Id: Ib82c235e4ba7dc75ee96a7abc0c47eff7b0a9013 Reviewed-by: hjk <hjk@qt.io>
* qmake: move over from QmakeProjectNodes to QmakeParserNodesTobias Hunger2017-02-221-5/+5
| | | | | | Change-Id: Iab87e0c248b0f651a1774336c3bddf83baa9d057 Reviewed-by: hjk <hjk@qt.io> Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
* qmake: Use ProjectType enum consistentlyTobias Hunger2017-02-141-5/+4
| | | | | Change-Id: I633a7150202fcbf420a33b4173d2b4451f46eb11 Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
* Move CustomExecutableRunConfiguration to ProjectExplorerhjk2016-05-131-4/+4
| | | | | | | There's nothing QtSupport specific in there. Change-Id: I616a37ed56f1853cdbb16f483de5682d5ea63715 Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* Debugger: Merge debug mode and analyze modehjk2016-03-071-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | On the user-visible side, only the 'Analyze' mode button disappears, and instead a combobox to switch between different tools in appears in the Debug mode toolbar. Internally, that's quite some re-organzition: The centralized 'Analyze mode is busy' flag is gone, allowing us to run e.g. ClangStaticAnalyzer and MemCheck in parallel. Analyzer tools and debugger now share the same mechanism to generate/load/save dock widgets. Analyzer tools now create and handle their own start/stop button when appropriate. In general, Analyzer tools can create/handle more than one run control at a time. Further consolidation is possible, e.g. RunControl state handling could be merged into the base ProjectExplorer::RunControl to avoid the still existing duplication in ~15 instances. Change-Id: I91e5940ebc4211f98056d507cf2f7b5f8efe7f07 Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Move analyzerbase to debuggerhjk2016-02-251-3/+3
| | | | | | | | | | | | This is the first mechanical step to execute on the 'shared pool of debugger/analyzer views' idea. Future steps would be providing infrastructure for the view pool, making all analyzer/debugger views use the pool and then re-extract a sensible base for a 'analyzer-and/or-debugger' tool plugin interface. Change-Id: I1bb392e6dd3084fc56937956bee1d6fd9530335d Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>
* Analyzer: Remove AnalyzerRunControl::runnable() and .connection()hjk2016-01-291-0/+2
| | | | | | | | These re-implementations are conceptually "too specific". Rather let the indiviual tools handle there expectations themselves. Change-Id: I0bbea407b2241816a40d19eb1dbb0a7589cbda7b Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Analyzer: Use a StandardRunnable instead of an AnalyzerRunnablehjk2016-01-271-3/+3
| | | | | | | ... with a lot potential to code consolidation. Change-Id: I4d3a7fcc1cc6ae8763799f18cf9701695f387791 Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Ios: Adapt IosRunControlFactory to Analyzer changeshjk2016-01-201-2/+23
| | | | | Change-Id: I6aed9afaffadc33bec63d798b3f1f7e525a7f790 Reviewed-by: Alessandro Portale <alessandro.portale@theqtcompany.com>
* Update License according to agreement with Free Qt FoundationTobias Hunger2016-01-191-17/+12
| | | | | | | * Update files in src/plugins Change-Id: Ia5d77fad7d19d4bb3498e78661982f68729adb22 Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
* ProjectNode: Rename path() to filePath()Tobias Hunger2015-11-031-1/+1
| | | | | Change-Id: I78bb73f8c9457fd74c470eacbf54eb9195ac9681 Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>
* ProjectExplorer: Use Core::Id as RunMode "enum values"BogDan Vatra2015-06-301-6/+10
| | | | | | | | | | | | | This provides a way for third-party plugins to implement run modes without the need to add a value to the central enum or using manual workarounds like RunMode(*(int*)&someUniqueObject). Instead of centrally defined enum values this uses Core::Id that could be defined anywhere. Change-Id: Ic350e3d8dbb8042c61b2d4ffec993ca151f53099 Reviewed-by: Daniel Teske <daniel.teske@theqtcompany.com> Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>
* Don't allow to run static libs.BogDan Vatra2015-03-231-1/+1
| | | | | | | | Static libs can't be run on Android and on iOS, so we need to filter them out. Change-Id: I90b778ffaa5e7d6267cc0e8d753be56bf93007a7 Reviewed-by: Daniel Teske <daniel.teske@theqtcompany.com>
* ProjectExplorer: Use FileName for Node::pathOrgad Shaneh2015-02-131-8/+10
| | | | | | Change-Id: I4a41cfb629be8bb06b4b0616cd4475525e617a51 Reviewed-by: BogDan Vatra <bogdan@kde.org> Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>
* Merge commit '3c85058694ee2e41658d17f524fb48f0b187d2fe'Eike Ziller2015-02-121-6/+6
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: src/libs/utils/tooltip/tipcontents.cpp src/libs/utils/tooltip/tipcontents.h src/plugins/android/androiddeployqtstep.cpp src/plugins/baremetal/baremetalconstants.h src/plugins/baremetal/baremetaldevice.cpp src/plugins/baremetal/baremetaldevice.h src/plugins/baremetal/baremetaldeviceconfigurationwidget.cpp src/plugins/baremetal/baremetaldeviceconfigurationwidget.h src/plugins/baremetal/baremetaldeviceconfigurationwizard.cpp src/plugins/baremetal/baremetaldeviceconfigurationwizardpages.cpp src/plugins/baremetal/baremetaldeviceconfigurationwizardpages.h src/plugins/baremetal/baremetalplugin.cpp src/plugins/baremetal/baremetalplugin.h src/plugins/baremetal/baremetalruncontrolfactory.cpp src/plugins/baremetal/baremetalruncontrolfactory.h src/plugins/cppeditor/cppcodemodelinspectordialog.cpp src/plugins/cppeditor/cppdoxygen_test.cpp src/plugins/cppeditor/cppdoxygen_test.h src/plugins/debugger/breakpointmarker.cpp src/plugins/debugger/debuggeritemmodel.cpp src/plugins/debugger/debuggeritemmodel.h src/plugins/debugger/loadcoredialog.cpp src/plugins/genericprojectmanager/cppmodelmanagerhelper.cpp src/plugins/projectexplorer/addnewmodel.cpp src/plugins/projectexplorer/addnewmodel.h src/plugins/projectexplorer/jsonwizard/jsonfieldpage.cpp src/plugins/qmlprofiler/abstracttimelinemodel.cpp src/plugins/qmlprofiler/abstracttimelinemodel.h src/plugins/qmlprofiler/notesmodel.cpp src/plugins/qmlprofiler/qml/CategoryLabel.qml src/plugins/qmlprofiler/qml/MainView.qml src/plugins/qmlprofiler/qml/Overview.js src/plugins/qmlprofiler/qml/Overview.qml src/plugins/qmlprofiler/qml/TimeDisplay.qml src/plugins/qmlprofiler/qml/TimeMarks.qml src/plugins/qmlprofiler/qmlprofilertimelinemodelproxy.cpp src/plugins/qmlprofiler/sortedtimelinemodel.cpp src/plugins/qmlprofiler/sortedtimelinemodel.h src/plugins/qmlprofiler/timelinemodelaggregator.cpp src/plugins/qmlprofiler/timelinemodelaggregator.h src/plugins/qmlprofiler/timelinerenderer.cpp src/plugins/qmlprofiler/timelinerenderer.h src/plugins/qmlprojectmanager/QmlProjectManager.json.in src/plugins/texteditor/findinfiles.cpp src/plugins/vcsbase/vcsconfigurationpage.cpp src/shared/qbs src/shared/scriptwrapper/interface_wrap_helpers.h src/shared/scriptwrapper/wrap_helpers.h tests/auto/qmlprofiler/abstracttimelinemodel/tst_abstracttimelinemodel.cpp tests/system/suite_debugger/tst_debug_empty_main/test.py tests/system/suite_debugger/tst_qml_js_console/test.py tests/system/suite_debugger/tst_qml_locals/test.py Change-Id: I67540b648f8b162496f4aa606b04d50c7c9125c6
| * Update LicenseEike Ziller2015-01-161-6/+6
| | | | | | | | | | Change-Id: I711d5fb475ef814a1dc9d2822740e827f3f67125 Reviewed-by: Alessandro Portale <alessandro.portale@digia.com>
* | IOS: Remove unneeded qualificationsOrgad Shaneh2015-02-051-6/+6
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | Mostly done using the following ruby script: Dir.glob('**/*.cpp').each { |file| next if file =~ %r{src/shared/qbs|/qmljs/} s = File.read(file) s.scan(/^using namespace (.*);$/) { ns = $1 t = s.gsub(/^(.*)\b#{ns}::((?!Const)[A-Z])/) { |m| before = $1 char = $2 if before =~ /"|\/\/|\\|using|SIGNAL|SLOT|Q_/ m else before + char end } if t != s puts file File.open(file, 'w').write(t) end } } Change-Id: I8ef73f4861069dcd7edf5e73b397d60609d4b476 Reviewed-by: Fawzi Mohamed <fawzi.mohamed@theqtcompany.com>
* License updateEike Ziller2014-10-091-7/+8
| | | | | Change-Id: I3c22ef2685d7aa589f5d0ab74d693653a4c32082 Reviewed-by: Alessandro Portale <alessandro.portale@digia.com>