Ide/Project Settings - Revision history

Boris Belov: /* Project Name */

2019-09-09T14:13:22Z

Project Name

← Older revision		Revision as of 16:13, 9 September 2019
Line 15:		Line 15:
	=== Project Name ===		=== Project Name ===

	The project name must be specified in the '''Project Name''' option while a project creation. '''Project Settings''' uses this project name to generate name for the project file: <vpbnf><ProjectName>.~~prj6~~</vpbnf>. The specified project name is also used as the default name of '''Subdirectory''' in which the project is placed.		The project name must be specified in the '''Project Name''' option while a project creation. '''Project Settings''' uses this project name to generate name for the project file: <vpbnf><ProjectName>.vipprj</vpbnf>. The specified project name is also used as the default name of '''Subdirectory''' in which the project is placed.

	=== Project Kind ===		=== Project Kind ===

Thomas Linder Puls: /* Run Options Tab /

2013-09-04T11:42:35Z

Run Options Tab: *

← Older revision		Revision as of 13:42, 4 September 2013
Line 189:		Line 189:

	*'''Run Arguments'''		*'''Run Arguments'''
	:Here it is possible to specify command line parameters that will be passed to the target application when it starts from the IDE.		*:Here it is possible to specify command line parameters that will be passed to the target application when it starts from the IDE.
	*'''Executable for Run/Debugger'''		*'''Executable for Run/Debugger'''
	:Here you can specify an executable filename that will be loaded by the IDE for debugging.		*:Here you can specify an executable filename that will be loaded by the IDE for debugging.
	*'''External Project for Debugger'''		*'''External Project for Debugger'''
	:Here you can specify a project with the debug information that should be used by the IDE while debugging.		*:Here you can specify a project with the debug information that should be used by the IDE while debugging.
	*'''Working Directory for Run/Debug'''		*'''Working Directory for Run/Debug'''
	:If this option is set, a user application will use this directory as a working directory for Run/Debug comands, otherwise the final directory will be used. If the relative path is defined then the path is calculated from the project directory.		*:If this option is set, a user application will use this directory as a working directory for Run/Debug comands, otherwise the final directory will be used. If the relative path is defined then the path is calculated from the project directory.

SergeMukhin: /* Run Options Tab */

2013-09-03T10:40:29Z

Run Options Tab

← Older revision		Revision as of 12:40, 3 September 2013
Line 189:		Line 189:

	*'''Run Arguments'''		*'''Run Arguments'''
	*:Here it is possible to specify command line parameters that will be passed to the target application when it starts from the IDE.		:Here it is possible to specify command line parameters that will be passed to the target application when it starts from the IDE.
	*'''Executable for Debugger'''		*'''Executable for Run/Debugger'''
	*:Here you can specify an executable filename that will be loaded by the IDE for debugging.		:Here you can specify an executable filename that will be loaded by the IDE for debugging.
	*'''External Project for Debugger'''		*'''External Project for Debugger'''
	*:Here you can specify a project with the debug information that should be used by the IDE while debugging.		:Here you can specify a project with the debug information that should be used by the IDE while debugging.
	*'''Working Directory for Run/Debug'''		*'''Working Directory for Run/Debug'''
	*:If this option is set, a user application will use this directory as a working directory for Run/Debug comands, otherwise the final directory will be used. If the relative path is defined then the path is calculated from the project directory.		:If this option is set, a user application will use this directory as a working directory for Run/Debug comands, otherwise the final directory will be used. If the relative path is defined then the path is calculated from the project directory.

Thomas Linder Puls: links

2013-06-13T14:45:23Z

links

← Older revision		Revision as of 16:45, 13 June 2013
Line 122:		Line 122:

	<vipbnf>pack->obj:$(Compiler) /L:R /L:I /L:STAT $(IncDir) /MAXE:200 /MAXW:1000		<vipbnf>pack->obj:$(Compiler) /L:R /L:I /L:STAT $(IncDir) /MAXE:200 /MAXW:1000
	"$*.pack" /OBJECTFILE:"$(ObjDir)$.obj" /DEBUGFILE:"$(ObjDir)$*.deb" /debug:full</vipbnf>		"$*.pack" /OBJECTFILE:"$(ObjDir)$.obj" /DEBUGFILE:"$(ObjDir)$*.deb" /debug:full</vipbnf>

	For more information about {{ide\|Make Facility#Make Rules\|Rules}} syntax see the {{ide\|Make Facility\|Make Facility}}.		For more information about {{ide\|Make Facility#Make Rules\|Rules}} syntax see the {{ide\|Make Facility\|Make Facility}}.
Line 137:		Line 137:
	=== Definition (.def) File ===		=== Definition (.def) File ===

	'''[$(DEF_FILE)]''': A {{ide\|~~IDE~~ Tools#Definition Files\|module-definition}} ('''.DEF''') file provides additional input for the linker. The module-definition files describe the essential characteristics of a target application or library.		'''[$(DEF_FILE)]''': A {{ide\|Command Line Tools#Definition Files\|module-definition}} ('''.DEF''') file provides additional input for the linker. The module-definition files describe the essential characteristics of a target application or library.

	Ordinary module-definition files should be used when the project target is a DLL or when the target file should use DLLs.		Ordinary module-definition files should be used when the project target is a DLL or when the target file should use DLLs.

	When the project target is a DLL, then names of all predicates exported from the DLL have to be added to the {{ide\|~~IDE~~ Tools#Definition Files\|EXPORT}} section of the module-definition file, which is used to build the DLL.		When the project target is a DLL, then names of all predicates exported from the DLL have to be added to the {{ide\|Command Line Tools#Definition Files\|EXPORT}} section of the module-definition file, which is used to build the DLL.

	When an import library is included into the project modules, then the correspondent DLL is linked statically to the application (load-time linking). Such projects must have module-definition files, whose {{ide\|~~IDE~~ Tools#Definition Files\|IMPORTS}} sections should specify names of all predicates imported from the DLL.		When an import library is included into the project modules, then the correspondent DLL is linked statically to the application (load-time linking). Such projects must have module-definition files, whose {{ide\|Command Line Tools#Definition Files\|IMPORTS}} sections should specify names of all predicates imported from the DLL.

	See {{ide\|~~IDE~~ Tools#Definition Files\|Definition Files}} in the {{ide\|~~IDE~~ Tools#Command Line Linker\|Command Line Linker}} for more information.		See {{ide\|Command Line Tools#Definition Files\|Definition Files}} in the {{ide\|Command Line Tools#Command Line Linker\|Command Line Linker}} for more information.

	=== Type Library File ===		=== Type Library File ===
Line 185:		Line 185:
	*#'''Private Build'''		*#'''Private Build'''
	*#:This flag means that the target file was built for private purpose.		*#:This flag means that the target file was built for private purpose.



	== Run Options Tab ==		== Run Options Tab ==

Thomas Linder Puls: links

2013-06-13T14:42:50Z

links

← Older revision		Revision as of 16:42, 13 June 2013
Line 133:		Line 133:
	-M"$(ObjDir)$.map" $(PROJECT_OBJ) "$(ObjDir)$.res" $(PROJECT_LIB)<<</vipbnf>		-M"$(ObjDir)$.map" $(PROJECT_OBJ) "$(ObjDir)$.res" $(PROJECT_LIB)<<</vipbnf>

	For more information about {{ide\|Make Facility#Build Script\|Build Scripts}} see the '''Make Facility''', the {{ide\|~~IDE~~ Tools#Command Line Compiler\|Command Line Compiler}}, and the {{ide\|~~IDE~~ Tools#Command Line Linker\|Command Line Linker}}.		For more information about {{ide\|Make Facility#Build Script\|Build Scripts}} see the '''Make Facility''', the {{ide\|Command Line Tools#Command Line Compiler\|Command Line Compiler}}, and the {{ide\|Command Line Tools#Command Line Linker\|Command Line Linker}}.

	=== Definition (.def) File ===		=== Definition (.def) File ===

Gukalov: /* File Templates Tab */

2013-05-16T13:22:34Z

File Templates Tab

← Older revision		Revision as of 15:22, 16 May 2013
Line 186:		Line 186:
	*#:This flag means that the target file was built for private purpose.		*#:This flag means that the target file was built for private purpose.

	~~== File Templates Tab ==~~

	*'''Comment Header'''
	*:The text from this file will be added as a header to each created Visual Prolog source file.
	*'''Interface Declaration'''
	*:The text from this file will be added as a header to each created interface declaration file.
	*'''Class Declaration'''
	*:The text from this file will be added as a header to each created class declaration file.
	*'''Class Implementation'''
	*:The text from this file will be added as a header to each created class implementation file.

	== Run Options Tab ==		== Run Options Tab ==

GalinaTchekmareva at 11:48, 18 April 2013

2013-04-18T11:48:36Z

Show changes

Gukalov at 13:06, 17 April 2013

2013-04-17T13:06:45Z

← Older revision		Revision as of 15:06, 17 April 2013
Line 6:		Line 6:

	== General Tab ==		== General Tab ==
	~~{{ideNavbar\|IDE Project Settings General Tab}}~~

	When creating a new project the sheet looks like:		When creating a new project the sheet looks like:

Gukalov at 13:06, 17 April 2013

2013-04-17T13:06:05Z

← Older revision		Revision as of 15:06, 17 April 2013
Line 6:		Line 6:

	== General Tab ==		== General Tab ==
			{{ideNavbar\|IDE Project Settings General Tab}}

	When creating a new project the sheet looks like:		When creating a new project the sheet looks like:

GalinaTchekmareva at 12:27, 6 March 2013

2013-03-06T12:27:51Z

← Older revision		Revision as of 14:27, 6 March 2013
Line 205:		Line 205:
	*'''External Project for Debugger'''		*'''External Project for Debugger'''
	*:Here you can specify a project with the debug information that should be used by the IDE while debugging.		*:Here you can specify a project with the debug information that should be used by the IDE while debugging.
	*'''Working Directory for Run/Debug'		*'''Working Directory for Run/Debug'''
	*:If this option is set, a user application will use this directory as a working directory for Run/Debug comands, otherwise the final directory will be used. If the relative path is defined then the path is calculated from the project directory.		*:If this option is set, a user application will use this directory as a working directory for Run/Debug comands, otherwise the final directory will be used. If the relative path is defined then the path is calculated from the project directory.

Ide/Project Settings - Revision history

Boris Belov: /* Project Name */

Thomas Linder Puls: /* Run Options Tab */ *

SergeMukhin: /* Run Options Tab */

Thomas Linder Puls: links

Thomas Linder Puls: links

Gukalov: /* File Templates Tab */

GalinaTchekmareva at 11:48, 18 April 2013

Gukalov at 13:06, 17 April 2013

Gukalov at 13:06, 17 April 2013

GalinaTchekmareva at 12:27, 6 March 2013

Thomas Linder Puls: /* Run Options Tab /