Building An Executable - Revision history

Paul Robinson: /* Periodic NARS Updates */

2019-10-13T21:09:38Z

Periodic NARS Updates

← Older revision		Revision as of 17:09, 13 October 2019
Line 330:		Line 330:
	# Also revisit '''[[#Pre_First_Compile_and_Localization_Notes\|Pre First Compile and Localization Notes]]''' and text edit file \trunk\wcustomize.bat to localize the new version.		# Also revisit '''[[#Pre_First_Compile_and_Localization_Notes\|Pre First Compile and Localization Notes]]''' and text edit file \trunk\wcustomize.bat to localize the new version.
	# Folder C:\NARS2000_old_rev may be '''Recycled''' after you are done copying non-trunk and non-msieve files/folders from it into your new C:\NARS2000 folder. If disk space is not restrictive and for 100% safety purposes, keep your prior folder available until after successfully '''Building/Compiling''' the newly downloaded 32-bit and 64-bit versions, and making sure you did not have any local personal changes now potentially being recycled.		# Folder C:\NARS2000_old_rev may be '''Recycled''' after you are done copying non-trunk and non-msieve files/folders from it into your new C:\NARS2000 folder. If disk space is not restrictive and for 100% safety purposes, keep your prior folder available until after successfully '''Building/Compiling''' the newly downloaded 32-bit and 64-bit versions, and making sure you did not have any local personal changes now potentially being recycled.

			[[Category:NARS 2000]]

Robert Wallick: Clarified download, install and use of Tortoise SVN at SourceForge

2016-12-19T19:27:07Z

Clarified download, install and use of Tortoise SVN at SourceForge

← Older revision		Revision as of 15:27, 19 December 2016
Line 22:		Line 22:
	==Update Notice==		==Update Notice==

	<font color=blue>Although it is not ~~an 'only~~ compiler - IDE choice,' the below uses '''Visual Studio 2013''' as its designated C/C++ Compiler and IDE(Integrated Developer's Environment, GUI/Graphical User Interface for programming). All source code compiles correctly and multiple APL workspaces have been tested for correct APL/NARS functionality. This page is current, up-to-date re NARS working with VS2013's compiler and standards. The conversion to VS2013 resulted in a more up-to-date (5 years[2008 to 2013] more current software technology) program for the GUI Builder and Compiler interface, including newer C/C++ programming standards. This has represented a major cyclical software upgrade and results in greater APL user functionality via improved C coding. Recent releases of NARS2000.exe (32 and 64-bit versions) are fully functional.</font>		<font color=blue>Although it is not the "ONLY compiler - IDE (integrated developer's environment) choice", the below uses '''Visual Studio 2013''' as its designated C/C++ Compiler and IDE(Integrated Developer's Environment, GUI/Graphical User Interface for programming). All source code compiles correctly and multiple APL workspaces have been tested for correct APL/NARS functionality. This page is current, up-to-date re NARS working with VS2013's compiler and standards. The conversion to VS2013 resulted in a more up-to-date (5 years[2008 to 2013] more current software technology) program for the GUI Builder and Compiler interface, including newer C/C++ programming standards. This has represented a major cyclical software upgrade and results in greater APL user functionality via improved C coding. Recent releases of NARS2000.exe (32 and 64-bit versions) are fully functional.</font>
	<div align="right"><span class="plainlinks" style="font-size:70%">v---- '''Useful Developer links:''' ----v<br>[http://svnbook.red-bean.com Version Control with Subversioning - Conceptual Gen Bkgnd.]<br>[http://sourceforge.net/p/forge/documentation/svn/ Source Forge Versioning Documentation] <br>[http://sourceforge.net/p/nars2000/code/HEAD/tree/trunk/ Source Forge NARS2000 Source Code]</span></div>		<div align="right"><span class="plainlinks" style="font-size:70%">v---- '''Useful Developer links:''' ----v<br>[http://svnbook.red-bean.com Version Control with Subversioning - Conceptual Gen Bkgnd.]<br>[http://sourceforge.net/p/forge/documentation/svn/ Source Forge Versioning Documentation] <br>[http://sourceforge.net/p/nars2000/code/HEAD/tree/trunk/ Source Forge NARS2000 Source Code]</span></div>

Line 79:		Line 79:
	# '''Zip Utility''': '''[http://www.7-zip.org/ 7-Zip]''' (Latest version, 32- or 64-bit, as appropriate to your system; needed to Extract/Unzip the files and folders you are downloading for this project.) If you already have a Zip utility program on your PC, Tablet or Server such as WinZip, you can normally skip the 7-Zip download/install.		# '''Zip Utility''': '''[http://www.7-zip.org/ 7-Zip]''' (Latest version, 32- or 64-bit, as appropriate to your system; needed to Extract/Unzip the files and folders you are downloading for this project.) If you already have a Zip utility program on your PC, Tablet or Server such as WinZip, you can normally skip the 7-Zip download/install.
	# '''PHP''' (Hypertext Preprocessor): '''[http://www.php.net/downloads.php Downloads]''' (<u>Windows downloads</u> for Windows systems.) (Windows binaries/VC9 x86 Thread Safe/Latest version/Zip or Installer, your choice) (Items to Install: Entire '''Script Executable''', and entire '''Extras'''). Place the unzipped file's contents into something like "C:\PHP". The executable file "php.exe" needs to be "on your directory or environmental path" when later compiling or building the APL executable.		# '''PHP''' (Hypertext Preprocessor): '''[http://www.php.net/downloads.php Downloads]''' (<u>Windows downloads</u> for Windows systems.) (Windows binaries/VC9 x86 Thread Safe/Latest version/Zip or Installer, your choice) (Items to Install: Entire '''Script Executable''', and entire '''Extras'''). Place the unzipped file's contents into something like "C:\PHP". The executable file "php.exe" needs to be "on your directory or environmental path" when later compiling or building the APL executable.
	# '''NARS2000 Source Code''': Click on '''[http://sourceforge.net/projects/nars2000/ Browse Code] button''' at '''NARS''' SourceForge.net '''code repository'''. You ~~may~~ also ~~use~~ a Version Control program, e.g. see Tortoise SVN below and [http://tortoisesvn.net/ here, ~~see their~~ download page]. <span class="plainlinks" style="font-size:70%"><br><u>'''Prior'''</u> non-current NARS Source Code versions available at [http://code.google.com/p/nars2000/source/checkout Code Google].</span>		# '''NARS2000 Source Code''': Click on '''[http://sourceforge.net/projects/nars2000/ Browse Code] button''' at '''NARS''' SourceForge.net '''code repository'''.
			## You also likely need a Version Control program for SourceForge code 'checkouts', e.g. see '''Tortoise SVN''' below and '''[http://tortoisesvn.net/ here, visit Tortoise SVN's download page]''', then download and install Tortoise SVN's 64-bit or 32-bit version depending on your operating system to subsequently be able to auto-check-out NARS source code. <span class="plainlinks" style="font-size:70%"><br><u>'''Prior'''</u> non-current NARS Source Code versions available at [http://code.google.com/p/nars2000/source/checkout Code Google].</span>
	# '''NARS2000 External Libraries''': [http://www.nars2000.org/download/binaries/misc.zip Miscellaneous Library] (misc.zip, which contains 4 .php files and 1 .ttf file - all directly unzipped into C:\NARS2000) and the following NARS libraries:		# '''NARS2000 External Libraries''': [http://www.nars2000.org/download/binaries/misc.zip Miscellaneous Library] (misc.zip, which contains 4 .php files and 1 .ttf file - all directly unzipped into C:\NARS2000) and the following NARS libraries:
	## [http://www.nars2000.org/download/binaries/mplibs.zip '''MPIR/MPFR/ECM Libraries'''] - These libraries(mplibs.zip) should be directly extracted or unzipped into the C:\NARS2000 folder such that three(3) distinct sub-directories are '''directly''' created: \ecm, \mpfr and \mpir, e.g. C:\NARS2000\ecm.		## [http://www.nars2000.org/download/binaries/mplibs.zip '''MPIR/MPFR/ECM Libraries'''] - These libraries(mplibs.zip) should be directly extracted or unzipped into the C:\NARS2000 folder such that three(3) distinct sub-directories are '''directly''' created: \ecm, \mpfr and \mpir, e.g. C:\NARS2000\ecm.
Line 117:		Line 118:

	An easy way to initialize your copy of the source code for the first time, although it may initially appear cumbersome to an SVN newcomer, is to use a version control program such as TortoiseSVN, mentioned above. One very helpful feature of TortoiseSVN is that it integrates well with Windows File Explorer. After downloading and installing TortoiseSVN and then rebooting your PC, there are two directories you will need to Install/initialize-checkout/TortoiseSVN-on.		An easy way to initialize your copy of the source code for the first time, although it may initially appear cumbersome to an SVN newcomer, is to use a version control program such as TortoiseSVN, mentioned above. One very helpful feature of TortoiseSVN is that it integrates well with Windows File Explorer. After downloading and installing TortoiseSVN and then rebooting your PC, there are two directories you will need to Install/initialize-checkout/TortoiseSVN-on.
	# '''First''' bring up Windows Explorer, right-click on the '''trunk''' folder you manually created, and choose '''SVN Checkout'''. The online NARS URL of repository: is '''svn://svn.code.sf.net/p/nars2000/code/trunk''' and your local Checkout directory: is '''C:\NARS2000\trunk''' (or wherever your trunk folder is) - quite likely you will have to edit the TortoiseSVN repository field or program local folder field because default text inserted by TortoiseSVN usually does not match folder location(s) identically. Depth should show Fully recursive, the default. To begin source code downloading/checkout into your locally created '''trunk''' folder click the '''OK''' button. Code downloading/checkout should then begin. With a high-speed Internet connection, time required to TortoiseSVN download/checkout NARS code is on the order of roughly two minutes. When successfully complete, you should get a return message at the end of the downloads list, like '''Completed at revision nnnn'''.		# '''First''' bring up Windows Explorer, right-click on the '''trunk''' folder you manually created, and choose '''SVN Checkout'''.
			## If you do not see "SVN Checkout" when you right-click on the '''trunk''' folder, download '''Tortoise SVN''' per the '''Tortoise SVN link above'''([[#Downloads\|Downloads-NARS2000 Source Code-Tortoise SVN]]. The online NARS SourceForge URL of source code repository: is '''svn://svn.code.sf.net/p/nars2000/code/trunk''' and your local Checkout directory: is '''C:\NARS2000\trunk''' (or wherever your trunk folder is) - quite likely you will have to edit the TortoiseSVN repository field or program local folder field because default text inserted by TortoiseSVN usually does not match folder location(s) identically. Depth should show Fully recursive, the default.
			## To begin source code downloading/checkout into your locally created '''trunk''' folder click the '''OK''' button. Code downloading/checkout should then begin. With a high-speed Internet connection, time required to TortoiseSVN download/checkout NARS code is on the order of roughly two minutes. When successfully complete, you should get a return message at the end of the downloads list, like '''Completed at revision nnnn'''.
	# '''Second''' (and this is a similar repeat step but using folder '''msieve''' instead of trunk), bring up Windows Explorer, right-click on the '''msieve''' folder you likewise manually created - and choose '''SVN Checkout...'''. This time online NARS '''URL of repository:''' is '''svn://svn.code.sf.net/p/nars2000/code/msieve''' (this address is slightly different than step 1) and your local '''Checkout directory:''' is '''C:\NARS2000\msieve''' (or wherever your '''msieve''' folder is). Again, depth should be fully recursive and click the '''OK''' button to begin. This step two normally completes in under five seconds, downloading far fewer files than the trunk download. Normally, the <u>same</u> msieve <u>revision</u> number should appear after finishing this download as per trunk download in step 1.		# '''Second''' (and this is a similar repeat step but using folder '''msieve''' instead of trunk), bring up Windows Explorer, right-click on the '''msieve''' folder you likewise manually created - and choose '''SVN Checkout...'''. This time online NARS '''URL of repository:''' is '''svn://svn.code.sf.net/p/nars2000/code/msieve''' (this address is slightly different than step 1) and your local '''Checkout directory:''' is '''C:\NARS2000\msieve''' (or wherever your '''msieve''' folder is). Again, depth should be fully recursive and click the '''OK''' button to begin. This step two normally completes in under five seconds, downloading far fewer files than the trunk download. Normally, the <u>same</u> msieve <u>revision</u> number should appear after finishing this download as per trunk download in step 1.

Robert Wallick: added NARS Systems Developer Knowledge Prerequisites section

2015-12-11T22:33:43Z

added NARS Systems Developer Knowledge Prerequisites section

← Older revision		Revision as of 18:33, 11 December 2015
Line 22:		Line 22:
	==Update Notice==		==Update Notice==

	<font color=blue>~~NARS Conversion from Visual Studio 2008 to~~ Visual Studio 2013 ~~is complete!~~ All source code compiles correctly and multiple APL workspaces have been tested for correct APL/NARS functionality. This page is current, up-to-date re NARS working with VS2013's compiler and standards. The conversion to VS2013 ~~results~~ in a more up-to-date (5 years more current software technology) program for the GUI Builder and Compiler interface, including newer C/C++ programming standards. This has represented a major cyclical software upgrade and results in greater APL user functionality via improved C coding. ~~The recent Beta~~ releases of NARS2000.exe (32 and 64-bit versions) are fully functional.</font>		<font color=blue>Although it is not an 'only compiler - IDE choice,' the below uses '''Visual Studio 2013''' as its designated C/C++ Compiler and IDE(Integrated Developer's Environment, GUI/Graphical User Interface for programming). All source code compiles correctly and multiple APL workspaces have been tested for correct APL/NARS functionality. This page is current, up-to-date re NARS working with VS2013's compiler and standards. The conversion to VS2013 resulted in a more up-to-date (5 years[2008 to 2013] more current software technology) program for the GUI Builder and Compiler interface, including newer C/C++ programming standards. This has represented a major cyclical software upgrade and results in greater APL user functionality via improved C coding. Recent releases of NARS2000.exe (32 and 64-bit versions) are fully functional.</font>
	<div align="right"><span class="plainlinks" style="font-size:70%">v---- '''Useful Developer links:''' ----v<br>[http://svnbook.red-bean.com Version Control with Subversioning - Conceptual Gen Bkgnd.]<br>[http://sourceforge.net/p/forge/documentation/svn/ Source Forge Versioning Documentation] <br>[http://sourceforge.net/p/nars2000/code/HEAD/tree/trunk/ Source Forge NARS2000 Source Code]</span></div>		<div align="right"><span class="plainlinks" style="font-size:70%">v---- '''Useful Developer links:''' ----v<br>[http://svnbook.red-bean.com Version Control with Subversioning - Conceptual Gen Bkgnd.]<br>[http://sourceforge.net/p/forge/documentation/svn/ Source Forge Versioning Documentation] <br>[http://sourceforge.net/p/nars2000/code/HEAD/tree/trunk/ Source Forge NARS2000 Source Code]</span></div>

Line 193:		Line 193:
	==Set Up VC++ Express==		==Set Up VC++ Express==

	If you are using VC++ Express, the project file is in the '''trunk''' folder and is called '''NARS2000.vcproj'''. You may load it manually every time you invoke VC++ Express, or you may load it automatically by placing the path to the project file on the command line in the VC++ Express shortcut as in '''"C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\VCExpress.exe" C:\NARS2000\trunk\NARS2000.vcproj''' or wherever you defined your NARS2000 root folder.		If you are using Visual Studio 2013/VC++ Express, the project file is in the '''trunk''' folder and is called '''NARS2000.vcproj'''. You may load it manually every time you invoke VC++ Express, or you may load it automatically by placing the path to the project file on the command line in the VC++ Express shortcut as in '''"C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\VCExpress.exe" C:\NARS2000\trunk\NARS2000.vcproj''' or wherever you defined your NARS2000 root folder.

	The vast majority of the project settings are found in the above file with some exceptions.		The vast majority of the project settings are found in the above file with some exceptions.
Line 289:		Line 289:
	Special note regarding '''w32.bat start''' and '''w64.bat start''' while in Visual Studio's IDE for the NARS2000 project:		Special note regarding '''w32.bat start''' and '''w64.bat start''' while in Visual Studio's IDE for the NARS2000 project:
	When <u>switching</u> between 32 and 64-bit versions, i.e. w32.bat start '''versus''' w64.bat start: There is a '''Property''' adjustment required when using Visual Studio's IDE. After Visual Studio opens up and in the Solution Explorer window (usually on the upper right hand side of your screen) click on "Solution 'nars2000' (1 project)." This should then show a Properties Window just below it. Look for a line which reads: '''Active config'''. If you ran w32.bat start then Active config should have a value of '''Debug32\|Win32'''. If you ran w64.bat start then Active config should have a value of '''Debug64\|Win32'''.		When <u>switching</u> between 32 and 64-bit versions, i.e. w32.bat start '''versus''' w64.bat start: There is a '''Property''' adjustment required when using Visual Studio's IDE. After Visual Studio opens up and in the Solution Explorer window (usually on the upper right hand side of your screen) click on "Solution 'nars2000' (1 project)." This should then show a Properties Window just below it. Look for a line which reads: '''Active config'''. If you ran w32.bat start then Active config should have a value of '''Debug32\|Win32'''. If you ran w64.bat start then Active config should have a value of '''Debug64\|Win32'''.

			== NARS Systems Developer Suggested Knowledge Prequisites ==

			For a strongly recommended set of knowledge prerequisites - in order to effectively understand, maintain or improve NARS functionality - please see '''[[NARS System Developer Suggested Knowledge Prerequisites\|NARS System Developer Suggested Knowledge Prerequisites]]'''.

	==Developer Experiments with NARS Source Code==		==Developer Experiments with NARS Source Code==

Robert Wallick: /* Platforms */ added TeamViewer / remote desktop software

2015-09-02T09:41:16Z

Platforms: added TeamViewer / remote desktop software

← Older revision		Revision as of 05:41, 2 September 2015
Line 43:		Line 43:
	==Platforms==		==Platforms==

	The current version of NARS2000 may be built on Windows platforms, including ~~a broad set of~~ Windows OS versions. Furthermore, a long-term goal is to enable NARS to be built on Linux, Mac OS, etc. as per user requests and Developer interests. If you do not have a Windows machine, the following may be helpful to you:		The current version of NARS2000 may be run and built on a variety of Windows platforms, including most or all post-Windows-98 OS versions. Furthermore, a long-term goal is to enable NARS to be built on Linux, Mac OS, etc. as per user requests and Developer interests. If you do not have a Windows machine, the following may be helpful to you:

	'''[http://www.howtogeek.com/187359/5-ways-to-run-windows-software-on-a-mac/ Five ways to run Windows software on a Mac.]''' From HowToGeek.com, methods include 1)Virtual Machines, 2)Boot Camp, 3)Wine, 4)CrossOver Mac (not free) and 5)Remote Desktop.		'''[http://www.howtogeek.com/187359/5-ways-to-run-windows-software-on-a-mac/ Five ways to run Windows software on a Mac.]''' From HowToGeek.com, methods include 1)Virtual Machines, 2)Boot Camp, 3)Wine, 4)CrossOver Mac (not free) and 5)Remote Desktop.
Line 50:		Line 50:

	'''[http://www.howtogeek.com/173353/how-to-run-windows-software-on-a-chromebook/ How to Run Windows Software on a Chromebook {notebook or tablet PC}.]''' Again from HowToGeek.com, methods include 1)Access a Windows Desktop Remotely, 2)Use Developer Mode and Install Wine (not available for all Chromebooks), 3)Use Developer Mode and Install a Virtual Machine (may require an Intel Chromebook).		'''[http://www.howtogeek.com/173353/how-to-run-windows-software-on-a-chromebook/ How to Run Windows Software on a Chromebook {notebook or tablet PC}.]''' Again from HowToGeek.com, methods include 1)Access a Windows Desktop Remotely, 2)Use Developer Mode and Install Wine (not available for all Chromebooks), 3)Use Developer Mode and Install a Virtual Machine (may require an Intel Chromebook).

			Furthermore, if you work using a tablet or other computing device which supports remote desktop software such as '''[http://teamviewer.com Team Viewer]''' and you have a home or work computer running Windows - then you can remotely use NARS over your network and internet using that computer as a host and your local device as a client. Network and internet speeds are sufficiently fast and TeamViewer, for instance, is very good at making your remote desktop seem and respond as if virtually right in front of you.

	For the present, the following sections detail descriptions for building the executable with bias towards Windows.		For the present, the following sections detail descriptions for building the executable with bias towards Windows.

Robert Wallick: /* Update Notice */ wording

2015-08-12T15:53:42Z

Update Notice: wording

← Older revision		Revision as of 11:53, 12 August 2015
Line 22:		Line 22:
	==Update Notice==		==Update Notice==

	<font color=blue>~~7/5/2015 Note:~~ NARS Conversion from Visual Studio 2008 to Visual Studio 2013 ~~should be substantially~~ complete. All source code ~~has compiled~~ correctly and ~~several~~ workspaces have been tested for correct APL/NARS functionality. This page ~~should be hopefully entirely complete/correct~~ re ~~updating~~ NARS to working with ~~Visual Studio 2013~~. The conversion to ~~using Visual Studio 2013~~ results in a more up-to-date (5 years more current software technology) program for the GUI Builder and Compiler interface, including newer C/C++ programming standards. This ~~represents in some ways~~ a major cyclical software upgrade and ~~will over the long-term result~~ in greater APL user functionality. The recent Beta releases of NARS2000.exe (32 and 64-bit versions) ~~should be~~ fully functional.</font>		<font color=blue>NARS Conversion from Visual Studio 2008 to Visual Studio 2013 is complete! All source code compiles correctly and multiple APL workspaces have been tested for correct APL/NARS functionality. This page is current, up-to-date re NARS working with VS2013's compiler and standards. The conversion to VS2013 results in a more up-to-date (5 years more current software technology) program for the GUI Builder and Compiler interface, including newer C/C++ programming standards. This has represented a major cyclical software upgrade and results in greater APL user functionality via improved C coding. The recent Beta releases of NARS2000.exe (32 and 64-bit versions) are fully functional.</font>
	<div align="right"><span class="plainlinks" style="font-size:70%">v---- '''Useful Developer links:''' ----v<br>[http://svnbook.red-bean.com Version Control with Subversioning - Conceptual Gen Bkgnd.]<br>[http://sourceforge.net/p/forge/documentation/svn/ Source Forge Versioning Documentation] <br>[http://sourceforge.net/p/nars2000/code/HEAD/tree/trunk/ Source Forge NARS2000 Source Code]</span></div>		<div align="right"><span class="plainlinks" style="font-size:70%">v---- '''Useful Developer links:''' ----v<br>[http://svnbook.red-bean.com Version Control with Subversioning - Conceptual Gen Bkgnd.]<br>[http://sourceforge.net/p/forge/documentation/svn/ Source Forge Versioning Documentation] <br>[http://sourceforge.net/p/nars2000/code/HEAD/tree/trunk/ Source Forge NARS2000 Source Code]</span></div>

Robert Wallick: /* Pre First Compile and Localization Notes */ command entered, emphasis added via enlarged font size

2015-08-11T16:13:55Z

Pre First Compile and Localization Notes: command entered, emphasis added via enlarged font size

← Older revision		Revision as of 12:13, 11 August 2015
Line 266:		Line 266:
	The additional hat(^) symbol in the above bat commands is needed for directory/folder recombination purposes, essentially sub-directory parse-point identification and or recombination point, where NARS may use subdirectories/parsing.		The additional hat(^) symbol in the above bat commands is needed for directory/folder recombination purposes, essentially sub-directory parse-point identification and or recombination point, where NARS may use subdirectories/parsing.

	'''Prior''' to using '''Visual Studio''' and its '''IDE'''(integrated developer's environment) for NARS Building/Compilation purposes a first time, and to help ensure the proper installation of NARS source code - it is very helpful/necessary to open a CMD.EXE window using '''Windows Start''', '''CMD.EXE'''. This will open up a small CMD window. While inside the opened CMD.EXE window, navigate to your local C:\NARS2000\trunk folder, using '''cd C:\NARS2000\trunk''' where cd represents change directory. Now run '''mk32.bat''' by typing it in, to compile NARS2000's 32-bit executable. If mk32.bat is successful and if your installation is 100% correct, two identical files in separate folders will be created(built and compiled) using bat commands from inside that CMD window/session:<br>		'''Prior''' to using '''Visual Studio''' and its '''IDE'''(integrated developer's environment) for NARS Building/Compilation purposes a first time, and to help ensure the proper installation of NARS source code - it is very helpful/necessary to open a CMD.EXE window using <big>'''Windows Start''', '''CMD.EXE'''</big>. This will open up a small CMD window. While <big>inside the opened CMD.EXE window</big>, navigate to your local C:\NARS2000\trunk folder, using <big>'''cd C:\NARS2000\trunk'''</big> where cd represents change directory. Now run <big>'''mk32.bat'''</big> by typing it in, to compile NARS2000's 32-bit executable. If mk32.bat is successful and if your installation is 100% correct, two identical files in separate folders will be created(built and compiled) using bat commands from inside that CMD window/session:<br>
	'''C:\NARS2000\trunk\RET\ND32\NARS2000.exe'''<br>		'''C:\NARS2000\trunk\RET\ND32\NARS2000.exe'''<br>
	'''C:\NARS2000\trunk\binaries\ND32\NARS2000.exe'''<br><br>		'''C:\NARS2000\trunk\binaries\ND32\NARS2000.exe'''<br><br>
	If that 32-bit NARS make/build was successful, then from the same CMD.EXE window, type '''mk64.bat'''. This should likewise compile locally the '''64-bit''' NARS Executable, with again two resulting '''exe output files:'''<br>		If that 32-bit NARS make/build was successful, then from the same CMD.EXE window, type <big>'''mk64.bat'''</big>. This should likewise compile locally the '''64-bit''' NARS Executable, with again two resulting '''exe output files:'''<br>
	'''C:\NARS2000\trunk\RET\ND64\NARS2000.exe'''<br>		'''C:\NARS2000\trunk\RET\ND64\NARS2000.exe'''<br>
	'''C:\NARS2000\trunk\binaries\ND64\NARS2000.exe'''		'''C:\NARS2000\trunk\binaries\ND64\NARS2000.exe'''

Robert Wallick: wording /* Why Build Your Own */

2015-07-10T03:24:37Z

wording Why Build Your Own

← Older revision		Revision as of 23:24, 9 July 2015
Line 33:		Line 33:
	Personalize some already pretty amazing software for yourself, or share it with others and get '''their feedback''' for even greater insight and subsequent improvement. NARS version of APL already has over a quarter million lines of source code, subroutines, macros, functions, etc. - 50 years of sometimes intense and continuing evolution, so you are <u>not</u> creating something from undeveloped scratch, but inheriting and working from already highly evolved, rigidly disciplined concepts and rigorously debugged software over time.		Personalize some already pretty amazing software for yourself, or share it with others and get '''their feedback''' for even greater insight and subsequent improvement. NARS version of APL already has over a quarter million lines of source code, subroutines, macros, functions, etc. - 50 years of sometimes intense and continuing evolution, so you are <u>not</u> creating something from undeveloped scratch, but inheriting and working from already highly evolved, rigidly disciplined concepts and rigorously debugged software over time.

	'''APL/2''' has been used in physics, science, robotics, engineering, artificial intelligence, VLSI, financial, statistical and social science applications. NASA and ~~Astronomy~~ have used it.		'''APL/2''' has been used in physics, science, genetic engineering-DNA studies, advanced mathematics, robotics, engineering, artificial intelligence, image processing, bio-medicine, VLSI, financial, statistical and social science applications. NASA and Astronomers have used APL.

	Now APL/2 is 100% customizable. Perhaps you will be the first to customize APL to safely drive a vehicle, help save a life, make new discoveries or make some process(es) more efficient.		Now APL/2 is 100% customizable. Perhaps you will be the first to customize APL to safely drive a vehicle, help save a life, make new discoveries or make some process(es) more efficient.

Robert Wallick: wording /* Periodic NARS Updates */

2015-07-10T03:09:39Z

wording Periodic NARS Updates

← Older revision		Revision as of 23:09, 9 July 2015
Line 308:		Line 308:
	==Periodic NARS Updates==		==Periodic NARS Updates==

	<u>Incremental Update:</u><br>		<u>Incremental Update</u> - Method 1:<br>
	Periodically, NARS developers should ensure changes done by ~~others~~ get incorporated into their local working copy. This is the process of integrating/downloading changes from NARS SourceForge server '''to''' your local copy. Updating may be performed on single files, a set of selected files, or recursively on entire directory hierarchies. To update, select the files and/or '''directories''' you want (usually \trunk and or \msieve), right click and select '''TortoiseSVN → Update''' in the explorer context menu for that trunk or msieve folder. A window will pop up displaying the progress of the update as it runs. Changes done by other developers will be merged into your local files, '''keeping''' any changes you may have done to the same files - if you did not want to keep your local changes but do want to keep the downloaded changes, select TortoiseSVN and Revert '''prior''' to running TortoiseSVN Update. NARS repository at SourceForge is '''not''' affected by an update to your local copy. [http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-update.html Update Your Working Copy With Changes From Others]		Periodically, NARS APL interpreter developers should ensure changes done by other developers get incorporated into their local machine's source code working copy. This is the process of integrating/downloading changes from NARS SourceForge server '''<u>to</u>''' your local copy. Updating may be performed on single files, a set of selected files, or recursively on entire directory hierarchies. To update, select the files and/or '''directories''' you want (usually \trunk and or \msieve), right click and select '''TortoiseSVN → Update''' in the explorer context menu for that trunk or msieve folder. A window will pop up displaying the progress of the update as it runs. Changes done by other developers will be merged into your local files, '''keeping''' any changes you may have done to the same files - if you did not want to keep your local changes but do want to keep the downloaded changes, select TortoiseSVN and Revert '''prior''' to running TortoiseSVN Update. NARS repository at SourceForge is '''not''' affected by an update to your local copy. [http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-update.html Update Your Working Copy With Changes From Others]

	<u>Total Source Code Replacement:</u><br>		<u>Total Source Code Replacement</u> - Method 2:<br>
	For example from version ~~1325~~ to say version ~~1364~~ (note a significant revision/datetime gap between 1325 and 1364, hypothetically), whatever NARS latest revision number is. Total code replacement may be preferred over incremental updating when major structural changes or significant source code changes are newly in situ.<br><br>		For example from version r1325 to say version r1364 (note a significant revision/datetime gap between 1325 and 1364, hypothetically), whatever NARS latest revision number is. Total code replacement may be preferred over incremental updating when major structural changes or significant source code changes are newly in situ.<br><br>
	Total Replacement Process: Visually scan NARS source code page at http://sourceforge.net/p/nars2000/code/HEAD/tree/trunk/ and review the top 25 to 40 file entries or so, while mentally keeping track of the '''highest revision number found'''. If after your last/earlier TortoiseSVN Update, your local version number is lower than the latest revision number visually found online, then perform the following to update to the most recent NARS revision:		Total Replacement Process: Visually scan NARS source code page at http://sourceforge.net/p/nars2000/code/HEAD/tree/trunk/ and review the top 25 to 40 file entries or so, while mentally keeping track of the '''highest revision number found'''(e.g. r1379). If after your last/earlier TortoiseSVN Update, your local version number is lower than the latest revision number visually found online, then perform the following to update to the most recent NARS revision:
	# Rename your existing NARS folder to something approximating C:\NARS2000_old_rev		# Rename your existing NARS folder to something approximating C:\NARS2000_old_rev
	# Create an entirely new C:\NARS2000 folder		# Create an entirely new C:\NARS2000 folder

Robert Wallick: revised section

2015-07-05T20:08:10Z

revised section

← Older revision		Revision as of 16:08, 5 July 2015
Line 20:		Line 20:
	\|}		\|}
	</div>		</div>
	==Update Notice~~: June 23 2015~~==		==Update Notice==

	<font color=blue>~~Caution~~: This page ~~may not yet~~ be entirely complete re updating to Visual Studio 2013. ~~NARS is significantly close to having converted the Compiler used to build NARS executable from Visual Studio 2008~~ to Visual Studio 2013 ~~- resulting~~ in a more up-to-date (5 years more current software technology) for the GUI Builder and Compiler interface, including newer C++ programming standards. This represents in some ways a major cyclical software upgrade. ~~Stay tuned. In the meantime, the~~ recent Beta releases of NARS2000.exe (32 and 64-bit versions) ~~are~~ fully functional.</font>		<font color=blue>7/5/2015 Note: NARS Conversion from Visual Studio 2008 to Visual Studio 2013 should be substantially complete. All source code has compiled correctly and several workspaces have been tested for correct APL/NARS functionality. This page should be hopefully entirely complete/correct re updating NARS to working with Visual Studio 2013. The conversion to using Visual Studio 2013 results in a more up-to-date (5 years more current software technology) program for the GUI Builder and Compiler interface, including newer C/C++ programming standards. This represents in some ways a major cyclical software upgrade and will over the long-term result in greater APL user functionality. The recent Beta releases of NARS2000.exe (32 and 64-bit versions) should be fully functional.</font>
	<div align="right"><span class="plainlinks" style="font-size:70%">v---- '''Useful Developer links:''' ----v<br>[http://svnbook.red-bean.com Version Control with Subversioning - Conceptual Gen Bkgnd.]<br>[http://sourceforge.net/p/forge/documentation/svn/ Source Forge Versioning Documentation] <br>[http://sourceforge.net/p/nars2000/code/HEAD/tree/trunk/ Source Forge NARS2000 Source Code]</span></div>		<div align="right"><span class="plainlinks" style="font-size:70%">v---- '''Useful Developer links:''' ----v<br>[http://svnbook.red-bean.com Version Control with Subversioning - Conceptual Gen Bkgnd.]<br>[http://sourceforge.net/p/forge/documentation/svn/ Source Forge Versioning Documentation] <br>[http://sourceforge.net/p/nars2000/code/HEAD/tree/trunk/ Source Forge NARS2000 Source Code]</span></div>

Robert Wallick: wording, expansion /* Developer Experiments with NARS Source Code */

2015-07-05T19:57:11Z

wording, expansion Developer Experiments with NARS Source Code

← Older revision		Revision as of 15:57, 5 July 2015
Line 290:		Line 290:
	==Developer Experiments with NARS Source Code==		==Developer Experiments with NARS Source Code==

	This section is for Developers who have successfully downloaded NARS source code and want to Experiment with it, ~~yet~~ still ~~stay~~ synched-with or later synch-back-to NARS online source code - i.e. after experimenting/changing local PC source code. This is equivalent to a ChemLab 101 at home/home-office and cleaning up all experiments at the end of the chemistry class, except as it applies to software developers, NARS software developers, and or those inclined to experiment safely.		This section is for Developers who have successfully downloaded NARS source code and want to Experiment with it, or further develop NARS APL Interpreter's source code.

			For development and debugging purposes: You as APL Interpreter developer normally want to want to <u>first</u> write new source code/model using the <u>32-bit version</u> of NARS2000 (w32.bat start). This is because the 32-bit version is easier to debug than the 64-bit version; error messages can be less complex. Migrating '''correct source code''' forward from the 32-bit version to the 64-bit version is also easier than a reverse migration.

			You will also at some point still need to be synched-with or later synch-back-to NARS online source code - i.e. after experimenting/changing local PC source code. This is equivalent to a ChemLab 101 at home/home-office and cleaning up all experiments at the end of the chemistry class, except as it applies to software developers, NARS software developers, and or those inclined to experiment safely.

	Here is where Tortoise SVN provides excellent and time-tested source-code clean-up tools for your local PC, including '''Resolve, Revert, Clean up, and Undo changes'''. Pull up these TortoiseSVN utilities by navigating Windows File Explorer to directory C:\NARS2000. If you successfully previously downloaded and Installed TortoiseSVN and NARS2000 source code, as outlined earlier/above, you may right click on say the \trunk subfolder in C:\NARS2000. A mouse right-click on \trunk should show an option labeled TortoiseSVN. Further choosing/selecting TortoiseSVN should then reveal multiple clean up options - Resolve, Revert, Clean up and Undo changes.<br>'''TortoiseSVN Documentation on:'''<br>[http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-cleanup.html Clean up.]<br>[http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-revert.html Undo Changes.]<br>[http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-conflicts.html Resolving Conflicts.]<br>		Here is where Tortoise SVN provides excellent and time-tested source-code clean-up tools for your local PC, including '''Resolve, Revert, Clean up, and Undo changes'''. Pull up these TortoiseSVN utilities by navigating Windows File Explorer to directory C:\NARS2000. If you successfully previously downloaded and Installed TortoiseSVN and NARS2000 source code, as outlined earlier/above, you may right click on say the \trunk subfolder in C:\NARS2000. A mouse right-click on \trunk should show an option labeled TortoiseSVN. Further choosing/selecting TortoiseSVN should then reveal multiple clean up options - Resolve, Revert, Clean up and Undo changes.<br>'''TortoiseSVN Documentation on:'''<br>[http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-cleanup.html Clean up.]<br>[http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-revert.html Undo Changes.]<br>[http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-conflicts.html Resolving Conflicts.]<br>
Line 299:		Line 303:
	# Select '''Clean up''', check '''Refresh shell overlays''', click '''OK''', let it run.		# Select '''Clean up''', check '''Refresh shell overlays''', click '''OK''', let it run.
	Per TortoiseSVN there should again be green check marks appearing on your trunk folder as well as your msieve folder.		Per TortoiseSVN there should again be green check marks appearing on your trunk folder as well as your msieve folder.

			For revision tracking and long-term software program maintenance purposes: '''Keep track of which files (file names) you personally modify, including a brief purpose''' for that edit. You will need to this information later for Release Notes purposes (see folder C:\NARS2000\trunk\ReleaseNotes for best-practice-examples of developer note-taking) and if you later synch to a new online NARS version, you may have to carry-forward your edit changes into a newly downloaded set of NARS source code files which may or may not reflect your prior local computer edit changes.

	==Periodic NARS Updates==		==Periodic NARS Updates==