+16
-51
doc/languages-frameworks/bower.section.md
+16
-51
doc/languages-frameworks/bower.section.md
···In ["buildBowerComponents" example](#ex-buildBowerComponents) the following arguments are of special significance to the function:-<varname>generated</varname> specifies the file which was created by <command>bower2nix</command>.-<varname>src</varname> is your project's sources. It needs to contain a <filename>bower.json</filename> file.`buildBowerComponents` will run Bower to link together the output of `bower2nix`, resulting in a `bower_components` directory which can be used.······-bowerComponents = pkgs.buildBowerComponents { <co xml:id="ex-buildBowerComponentsDefault-1" />-cp --reflink=auto --no-preserve=mode -R $bowerComponents/bower_components . <co xml:id="ex-buildBowerComponentsDefault-2" />-Whether to symlink or copy the <filename>bower_components</filename> directory depends on the build tool in use. In this case a copy is used to avoid <command>gulp</command> silliness with permissions.+2. Whether to symlink or copy the {file}`bower_components` directory depends on the build tool in use.+4. The actual build command in this example is {command}`gulp`. Other tools could be used instead.
+7
-22
doc/languages-frameworks/qt.section.md
+7
-22
doc/languages-frameworks/qt.section.md
···-Import Qt modules directly, that is: <literal>qtbase</literal>, <literal>qtdeclarative</literal>, etc.-because the Qt versions of dependencies may not be coherent, causing build and runtime failures.+It is important to import Qt modules directly, that is: `qtbase`, `qtdeclarative`, etc. *Do not* import Qt package sets such as `qt5` because the Qt versions of dependencies may not be coherent, causing build and runtime failures.+Additionally all Qt packages must include `wrapQtAppsHook` in `nativeBuildInputs`, or you must explicitly set `dontWrapQtApps`.