Sponsored Content
Top Forums Programming Determining C/C++ License count Post 302417724 by Corona688 on Friday 30th of April 2010 11:12:51 AM
Old 04-30-2010
Might've helped if you posted in the AIX forum.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Determining file length

How can I determine what UNIX thinks the record size of any given file is?? (1 Reply)
Discussion started by: jbrubaker
1 Replies

2. Programming

determining the object files...

hello, is there a utility to determine which object files are used to create a binary executable file?let me explain, please: for ex. there are three files: a.o b.o c.o and these files are used to create a binary called: prg namely, a.o b.o c.o -> prg so, how can i determine these three... (1 Reply)
Discussion started by: xyzt
1 Replies

3. Solaris

determining miniroot revision

Hi guys I have a bunch of x4100's x4140's etc with solaris 10 update4 running on them but I suspect that when a lot of these boxes were originally built, the jumpstart process used an update2 miniroot, now as far as i understand it, the miniroot used at jumpstart is the miniroot that stays on... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

4. IP Networking

Help determining what's blocking ports

I'm fairly new to networking and am trying to figure our network out, as I was recently assigned to be network administrator where I work. I was trying to get utorrent to work but am not having success in figuring out what's blocking my ports. As of now, I'm getting connected from a mikrotik... (11 Replies)
Discussion started by: brandonros
11 Replies

5. Linux

Determining L2 cache size

Is there any way to know the L2 cache size from examinging to boot log. Here is my boot logLinux version 2.6.13-jaluna (root@localhost.localdomain) (gcc version 3.2.2) #4 Thu Apr 23 23:16:10 EDT 2009 TMS320DM643X port (C) VirtualLogix and others Designed for the EVMDM6437 board, Spectrum Digital... (3 Replies)
Discussion started by: mourya
3 Replies

6. Programming

determining the IP of a function

Is there a way to determine the "Instruction Pointer" of a function in c++, and if so can someone tell me? (5 Replies)
Discussion started by: neur0n
5 Replies

7. Shell Programming and Scripting

Updating the license tag in XML file with new license

Hi All, I have a XML file : System.xml in which I want to update the license tag with the new data from file licence.xml. The content of files is in following format: System.xml: <?xml version="1.0"?> <!DOCTYPE Configuration SYSTEM "SystemVariables.dtd"> <usageConfiguration... (2 Replies)
Discussion started by: Pramod_T
2 Replies

8. UNIX for Advanced & Expert Users

Best practice - determining what region you are on

Hello all, I have a question about what you think the best practice is to determine what region you are running on when you have a system setup with a DEV/TEST, QA, and PROD regions running the same scripts in all. So, when you run in DEV, you have a different directory structure, and you... (4 Replies)
Discussion started by: Rediranch
4 Replies

9. Shell Programming and Scripting

Determining length of string

I have this script which is very easy: file=`echo 01114` echo $file 01114 then I ran this if ; then echo "yes";fi it returned yes even though there are only 5 digits there So then I tried file=`echo abcd` echo $file abcd if ]; then echo "yes";fi if ]; then echo "yes";fi It... (2 Replies)
Discussion started by: newbie2010
2 Replies
lc(Mono 2.6)															      lc(Mono 2.6)

NAME
lc - Mono License Compiler SYNOPSIS
lc -c filename -t targetassembly [-i reference...] [-v] [-o outputpath] [-nologo] DESCRIPTION
lc tool is a license compiler for Mono. It's used to convert a licenses.licx file to a resource that can be embedded into an executable. When using commercial components for .NET they often require a license resource at runtime to make sure the developer was licensed to use this control. The most common way of making sure the component was properly licensed is by using license resources. At compile time the developer uses the lc tool to convert a licenses.licx file to a programname.exe.resources file and embed that as a managed resource during compilation. RUNTIME OPTIONS
The following options are available: --complist=filename, -c filename This option is used to specify the input file, the licenses.licx file to create a license reesource for. This option is required. The license compiler will read each line in this file and try to load the types specified on that line. --target=assemblyname, -t targetassembly full assembly name with file extension for the target assembly. The license compiler uses this as a key when compiling the licenses. It has to match the assembly the resource will be embedded in. This option is required. --load=reference, -i reference Assembly reference to load before trying to compile a license. This option is needed for assemblies where the references are not in the gac. Compilers should pass all references to the license compiler. --verbose,, -v Gives more verbose output about the license compiling process. --help, -h Displays usage instructions. --output=path, -o path Target path file the licenses resource. By default the license compiler emits the resource in the current directory. The filename will always match the target assembly passed to --target with .licenses added. --nologo Do not emit the "Mono License Compiler" logo on stdout while compilng. LICENSE FILES
The format for the license files (licenses.licx) is the following: # comment namespace.type, assemblyname namespace.type, full-assemblyname All lines starting with a # are ignored. the first form requires that the assembly was loaded through the --load,-i option but does not require the full assembly name, only the first part. The second form requires the full assembly name including locale, version and publickeytoken. MAILING LISTS
Mailing lists are listed at the http://www.mono-project.com/Mailing_Lists WEB SITE
http://www.mono-project.com SEE ALSO
mono(1), mcs(1) lc(Mono 2.6)
All times are GMT -4. The time now is 11:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy